# Optimize an animated GIF

Shrink an animated GIF by using fewer colours, a smaller size or fewer frames, and see how much was saved.

- Endpoint: `POST https://setget.net/v1/tools/gif-optimize` with JSON `{"input": {...}}` (add `"wait": 30` to hold the reply until the job finishes)
- MCP: `run_tool` with `slug` = `gif-optimize`
- Page: https://setget.net/tools/gif-optimize

## Files in, files out

This is a file tool. Its file inputs take file references, not file contents and not web addresses.

- Get a reference by uploading: `curl -T FILE https://setget.net/drop/` prints a line `ref  <id>/f1`. Or `POST https://setget.net/v1/drops` with `{"files":[{"name","size"}]}`, PUT the bytes to the returned `upload.url` with the listed headers, and use the file's `ref`. Over MCP use the `drop` tool. A file under about 700 KB can also be sent in place as a `data:<type>;base64,<content>` URI.
- Uploads are at most 100 MB per file, are readable by anyone with the link, and expire (one hour by default). Programs are refused.
- The tool runs as a job. The reply is `{"tool", "ms", "result", "files", "job"}`: `result` is JSON, and every result file comes back in `files` as `{"name", "size", "content_type", "kind", "url", "ref"}`. Download it from `url`, or pass `ref` as the input of another file tool.
- A job still running when the wait ends answers 202 with `job`. Follow it with `GET https://setget.net/v1/jobs/<id>?wait=30`, or stream progress from `GET https://setget.net/v1/jobs/<id>/events` (over MCP: the `job` tool). A person can watch it at `job.url`.

## Inputs

- `image` (required, file, a file reference such as `DROP_ID/f1`, accepts image): The GIF to shrink.
- `colors` (optional, integer, default `128`, range 2..256): Colours in the result, 2-256. Fewer colours make a smaller file.
- `scale` (optional, integer, default `100`, range 5..100): Size of the result as a percentage of the original width and height.
- `drop_frames` (optional, integer, default `1`, range 1..20): Keep every Nth frame: 1 keeps all, 2 keeps every second frame. Kept frames are shown longer, so the animation runs at the same speed.

## Example 1: Reduce to 32 colours

Upload first. Each placeholder below stands for the reference of one upload: `DROP_ID/f1` = [sample.gif](https://setget.net/static/samples/sample.gif).

```json
{"input":{"image":"DROP_ID/f1","colors":32},"wait":30}
```

## Example 2: Half size, every second frame

Upload first. Each placeholder below stands for the reference of one upload: `DROP_ID/f1` = [sample.gif](https://setget.net/static/samples/sample.gif).

```json
{"input":{"image":"DROP_ID/f1","colors":64,"scale":50,"drop_frames":2},"wait":30}
```

**Which setting saves the most?** Scale: 50 percent leaves a quarter of the pixels. Dropping frames comes next, then colours. For the smallest file of all, convert to WebP with animated-convert.

**Can the result be larger than the original?** Occasionally, if the original was already tightly optimised and you change nothing. The result says so: saved_percent is then negative.

**Does dropping frames speed the GIF up?** No. Each kept frame is shown for the time of the frames it replaces.

**Does it work on WebP animations?** No, GIF only. Use animated-convert for other formats.
