TIFF to JSON Converter: Free, Private, No Upload
Convert TIFF files to JSON in your browser. Smaller output file, batch up to 20 files at once, no upload, no account, no watermark. Your files never leave your device.
- TIFF to JSON
- Batch up to 20 files
- No upload, no account
- Metadata stripped
- 1Add up to 20 images
- 2Pick from 18 formats
- 3Download or copy the code
Processed on your device. Your images are never uploaded, and metadata is stripped. How we keep it private
How do I convert TIFF to JSON for free?
Drop your TIFF files into the tool above, choose JSON as output, and download the result. Everything runs in your browser, so nothing is uploaded and there is no limit or watermark. It works on Windows, Mac, Linux, ChromeOS, iOS and Android — anywhere you have a modern browser.
- Price
- Free, no credits and no daily cap
- Account required
- No
- File uploaded to server
- No, processed locally in your browser
- Batch limit
- Up to 20 files at once
- Input format
- TIFF
- Output format
- JSON
- Best for
- JSON workflows, smaller files, faster sharing
- Works on
- Chrome, Edge, Firefox, Safari, iOS and Android browsers
- Privacy
- No upload, no tracking, metadata stripped
- Output quality
- Adjustable 1-100, defaults to 90
How to convert TIFF to JSON
- 1
Drop your TIFF files
Drag up to 20 TIFF files onto the page or click to choose them. Everything runs in your browser.
- 2
JSON is preselected
Output is already set to JSON. Adjust quality, resize or batch if you want.
- 3
Download
Save each JSON, or download all of them together as a ZIP.
TIFF to JSON: what changes and when it makes sense
TIFF is a Tagged Image File Format. It is best known for archival quality, high bit depth and CMYK support. The main drawbacks are large files and no display support in most browsers.
JSON is not an image format. It is a JSON value that wraps the image data as text. Its main appeal is carrying an image alongside other fields in a single payload. The main drawbacks are a size about a third larger than the original and slow parsing for large payloads.
TIFF vs JSON at a glance
| Property | TIFF | JSON |
|---|---|---|
| Type | Container format | Text encoding of an image |
| Compression | Flexible: uncompressed, lossless (LZW or ZIP) or JPEG-compressed | The image bytes are written out as Base64 text, which adds about 33 percent to the size |
| Transparency | Full alpha channel with soft edges | Same as the embedded image |
| Animation | No | Same as the embedded image |
| Colour depth | 8, 16 or 32 bits per channel, with CMYK, layers and multiple pages | Same as the embedded image |
| Support | Supported by professional editors, scanners and print workflows. Safari is the only major browser that displays it | Readable by every language and API client |
| History | Created by Aldus (later Adobe) in 1986 for desktop publishing and scanning. Owned by Adobe since 1994. Remains the professional standard for print, archival imaging and medical imaging. | JSON (JavaScript Object Notation) was specified by Douglas Crockford in 2001. Embedding images as base64 strings in JSON became common with REST APIs and AI model inputs (OpenAI vision, Anthropic Claude, Google Gemini). |
What actually changes in this conversion
- JSON is an encoding of the image data, not a new compression scheme. The text is about a third larger than the binary file, so what you gain is portability rather than a smaller size.
- Transparency follows the image data being encoded. JSON itself is only a text wrapper.
- Browser-based conversion works in 8-bit sRGB. Wide-gamut, 10-bit and 16-bit data are reduced. For colour-critical work, keep the original.
- EXIF, GPS and camera data are stripped on every conversion. That is good for privacy, but you lose capture dates.
About TIFF: history and technical details
Created by Aldus (later Adobe) in 1986 for desktop publishing and scanning. Owned by Adobe since 1994. Remains the professional standard for print, archival imaging and medical imaging.
Technical: Tag-based file structure with IFD (Image File Directory) entries. Supports CMYK, Lab, RGB, grayscale, bilevel. 8, 16, 32-bit depth. Multiple pages. Layers via extensions. Compression: none, LZW, ZIP, JPEG, PackBits.
Real-world size: A 300 DPI A4 scan is 25-50 MB as uncompressed TIFF. Same as PNG: 10-20 MB. As JPG at quality 90: 3-8 MB but with loss. Print workflows use TIFF because quality is preserved and CMYK is supported.
Popular tools: Adobe Photoshop, Adobe Illustrator, GIMP, ImageMagick, Capture One, Vuescan, SilverFast.
Alternatives: PNG (8-bit only, no CMYK), JPEG XL (future format), PSD (Photoshop native), PDF (for sharing).
About JSON: what you get
JSON (JavaScript Object Notation) was specified by Douglas Crockford in 2001. Embedding images as base64 strings in JSON became common with REST APIs and AI model inputs (OpenAI vision, Anthropic Claude, Google Gemini).
Technical: { "image": "iVBORw0KGgo...", "name": "photo.png" }. The base64 string can be escaped differently per language. Some APIs require no prefix, others require data:image/png;base64, prefix.
Real-world size: A 1 MB image as JSON base64 is ~1.33 MB. Parsing 10 MB JSON is 100-500ms in most languages. This is why vision AI APIs often recommend URL uploads for large images.
Popular tools: OpenAI API, Anthropic API, Google Gemini API, Postman, any JSON parser.
Alternatives: Multipart upload, Object storage + URL, Signed URL, Base64 in headers (rare).
Browser and software compatibility
TIFF: Supported by professional editors, scanners and print workflows. Safari is the only major browser that displays it. JSON: Readable by every language and API client.
JSON with an encoded image works with any parser. Large payloads parse slowly.
Why people move away from TIFF
- Browsers other than Safari cannot display TIFF, so it is unusable on web pages.
- TIFF files are huge. A single scan can run to hundreds of megabytes.
- Email clients and chat apps often cannot preview TIFF at all.
Why people choose JSON
- JSON with an encoded image is useful for API fixtures, config files and mock data.
- The image travels together with the other fields as a single payload.
Common mistakes with TIFF
- Using TIFF for web images — browsers will not display it
- Assuming all TIFFs are lossless — JPEG-compressed TIFF exists
- Ignoring bit depth — a 16-bit TIFF converted to 8-bit loses tonal range
Best practices for keeping quality
- TIFFs often hold 16-bit or CMYK data. Browser conversion works in 8-bit sRGB, so bit depth is reduced and colour can shift. For colour-critical work, use Photoshop or ImageMagick.
- Large payloads are slow to parse and send. Store files in object storage and keep a URL in the JSON for anything over a few hundred KB.
- Resize before converting if the image will be shown small. A 4000 pixel photo displayed at 800 pixels wastes bytes in any format.
- Check the result at 100 percent zoom, especially around text, edges and gradients, before you replace any originals.
- Keep your original files. Conversions to a lossy format cannot be undone.
- When you convert a set of images, use the same quality setting for the whole batch. The converter handles up to 20 files at once.
TIFF to JSON questions
Quick answers about privacy, quality, supported formats, file limits and how JSON works.
Why convert TIFF to JSON?
JSON files are typically smaller than TIFF, which makes them faster to share, send and load. The trade-off is a small amount of image detail at low quality settings.
Will converting TIFF to JSON lose quality?
At 90% quality, most people cannot tell the difference. Use 85-95% for photos and you are fine.
Does JSON keep transparency?
JSON is only a text wrapper around the image data, so transparency depends on the image format inside it.
Are my files uploaded?
Never. Everything runs in your browser. Your files never leave your device. Open DevTools Network tab while processing — you will see no upload request.
Can I convert many files at once?
Yes, up to 20 files at once. Download them individually or all together as a ZIP.
Does the converter strip metadata?
Yes. Browsers do not pass EXIF data through a canvas, so GPS, camera model and dates are removed on every conversion. That is good for privacy.
Is it free?
Yes. No credits, no daily cap, no account, no watermark. The practical limit is your device memory.
Do AI vision APIs accept base64 images?
Yes. OpenAI, Anthropic, and Google all accept base64 images in their API requests, either as a raw string or as a data URL depending on the provider. Check the specific API docs for the exact format.
Your files never leave your device
No upload, no account, no tracking. Everything happens in your browser using the Canvas API and WebAssembly. You can confirm this in your browser's DevTools Network tab while the tool runs — no request carries your file. See why ToolDeck is different.