# Split an image into tiles

Cut an image into a grid of tiles by rows and columns, or into tiles of a fixed pixel size.

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

## 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 image to cut up.
- `rows` (optional, integer, default `2`, range 1..100): Number of rows in the grid.
- `columns` (optional, integer, default `2`, range 1..100): Number of columns in the grid.
- `tile_width` (optional, integer, default `0`, range 0..16000): Width of each tile in pixels. Set this or tile_height to cut by size instead of by rows and columns. 0 means the full width.
- `tile_height` (optional, integer, default `0`, range 0..16000): Height of each tile in pixels. 0 means the full height.

## Example 1: 2 rows of 3 tiles

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

```json
{"input":{"image":"DROP_ID/f1","rows":2,"columns":3},"wait":30}
```

## Example 2: 256 pixel tiles

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

```json
{"input":{"image":"DROP_ID/f1","tile_width":256,"tile_height":256},"wait":30}
```

**What is the limit?** At most 100 tiles per run. Ask for fewer rows and columns, or larger tiles.

**What if the image does not divide evenly?** By rows and columns, tiles differ by at most one pixel. By pixel size, the last tile in each row and column is smaller.

**How are the tiles named?** After the image, with row and column counted from the top left: name-r1-c1, name-r1-c2 and so on.

**Which format are the tiles?** PNG, JPEG and WebP images keep their format. Everything else becomes PNG.
