What does it cost to convert TIFF to WebP?

$0.003 per call, paid in USDC on Base via x402.

How large can the TIFF file be?

Up to 25 MB (26,214,400 bytes). Past a limit the call answers too_large (413).

What happens if the conversion fails?

The tool answers with a typed JSON error from the errors table. Payment is settled only after the tool has produced its result; a call that fails inside the tool is never settled.

catalogue / tools / Images / TIFF to WebP

Convert TIFF to WebP

To convert TIFF to WebP, send one POST to /v1/image-convert with the TIFF source and "format": "webp" in the body. Each call costs $0.003 in USDC on Base via x402, with no account and no API key. The source file can be up to 25 MB.

Endpoint: POST /v1/image-convert
Price: $0.003 per call
Service: image-convert
Docs: /docs/image-convert

01Limits

Limit	Value
Largest source file	25 MB (26,214,400 bytes)
Timeout	60 s
Source formats	AVIF, GIF, JPEG, PNG, SVG, TIFF, WebP
Output formats	JPEG, PNG, WebP
Option quality	default 80

02Example

A real TIFF to WebP run of image-convert.

Request

POST /v1/image-convert
content-type: application/json
payment-signature: <base64 x402 payload>

{
  "url": "https://grist.tools/samples/images/pair-note.tiff",
  "quality": 80,
  "format": "webp"
}

Response

200 OK
payment-response: <base64 settlement receipt>

{
  "source_url": "https://grist.tools/samples/images/pair-note.tiff",
  "source_format": "tiff",
  "format": "webp",
  "mime_type": "image/webp",
  "width": 556,
  "height": 100,
  "bytes": 940,
  "image_base64": "UklGRqQDAABXRUJQVlA4IJgDAAAQPgCdASosAmQAPm0qkUW/oqGYf+wB+AbEtLdw..."
}

Source file: images/pair-note.tiff, 3.6 KB (3,690 bytes). LZW-compressed TIFF of the same 556x100 raster as ocr-scan.png: two uppercase lines drawn from a hand-written 5x7 bitmap font, SAMPLE SCAN FOR OCR and SECOND LINE 2026. The request sets quality to 80. The recorded run returned 940 bytes of WebP, 25% of the source size, with an image of 556x100 pixels. Decoded, the WebP in image_base64 opens with 52 49 46 46 A4 03 00 00 57 45 42 50 (ASCII RIFF and WEBP).

In the sample itself, the little-endian header points to a first image file directory at byte 3,476 with 15 entries; that directory declares 556 by 100 pixels, 3 samples per pixel and compression LZW. In the returned WebP: the RIFF header counts 932 bytes after itself, and the one chunk is a lossy VP8 bitstream of 920 bytes that starts with a key frame of 556 by 100 pixels.

03Format notes

TIFF as a source

TIFF states its byte order in the first four bytes: II followed by an asterisk and a NUL marks a little-endian file, MM followed by a NUL and an asterisk a big-endian one. image-convert and the OCR detector both accept either order. TIFF can wrap several internal compression schemes; Grist does not inspect them and leaves decoding to the bundled libvips loader, refusing with a typed error a file whose pixels will not decode rather than returning a partial result. Before that, the header dimensions are checked against the shared decoded-pixel budget, which is sized so that a high-resolution page scan still fits while a decompression bomb does not. TIFF is read but not written: image-convert's encode enum has no TIFF entry, so on these pages the format appears only as a source.

WebP as a target

Selecting WebP in image-convert always yields lossy WebP. The pinned options switch off lossless and near-lossless modes and smart subsampling, and fix the encoder effort so the search does not vary between builds; the caller's quality value is the one setting that changes the result. A lossless source such as PNG is therefore re-encoded lossily when WebP is the destination. The pixel grid stays as it was and the response reports width and height. Metadata blocks are removed because sharp is never asked to keep them, and animation is not written: the decoder reads the first frame only. Vector sources reach this encoder through image-convert, which rasterises them at sharp's default density with no density option, so an SVG becomes a WebP at its intrinsic size rather than at a caller-chosen resolution.

04Errors

Code	HTTP
`invalid_input`	`400`
`blocked_target`	`403`
`unreachable_target`	`424`
`upstream_timeout`	`424`
`unsupported_content_type`	`415`
`too_large`	`413`
`unprocessable`	`422`
`internal`	`500`

When each is raised, and what it means for payment: /docs/image-convert.

05Questions

What does it cost to convert TIFF to WebP?: $0.003 per call, paid in USDC on Base via x402.
How large can the TIFF file be?: Up to 25 MB (26,214,400 bytes). Past a limit the call answers too_large (413).
What happens if the conversion fails?: The tool answers with a typed JSON error from the errors table. Payment is settled only after the tool has produced its result; a call that fails inside the tool is never settled.