Open capability reference

What the browser can read, what FormatTailor can write.

A source-backed map of FormatTailor's image paths, safety limits, and privacy boundary. It documents the product as it exists; it does not pretend every browser or every file behaves the same.

Capability matrix

Product paths, not a browser popularity chart.

The table records what FormatTailor accepts and offers. “Runtime-dependent” means the page asks the current browser to do the work and checks the actual result instead of trusting a browser name or version.

How to read this:A green “Available” label still does not make a damaged file valid. AVIF and HEIC support is deliberately conditional. For browser-version data, use the maintained MDN compatibility dataset rather than copying a table that will go stale here.
FormatTailor image-format capabilities, reviewed 2026-08-21
FormatInputDecode pathOutputImportant limitEvidence
JPEG.jpg · .jpegAvailableBrowser-native image decoder.Runtime-dependentCanvas toBlob request for image/jpeg; returned MIME type is checked.JPEG output is lossy and transparent pixels require a chosen solid background.
PNG.pngAvailableBrowser-native image decoder.AvailableCanvas toBlob request for image/png; returned MIME type is checked.PNG is lossless, so photographic output can be much larger than JPEG or WebP.
WebP.webpRuntime-dependentBrowser-native image decoder.Runtime-dependentCanvas toBlob request for image/webp; silent PNG fallback is rejected.Encoding quality and file size vary by browser implementation and source content.
AVIF.avifRuntime-dependentBrowser-native image decoder only; there is no bundled AVIF fallback decoder.Not offeredA browser that cannot decode the selected AVIF file cannot use it in FormatTailor.
HEIC / HEIF.heic · .heifRuntime-dependentTry the browser decoder first, then the locally loaded heic2any decoder.Not offeredFormatTailor exports one decoded image; sequences, depth information, and unsupported variants may not survive or may fail to decode.
INPUT FILE40 MB

Interface limit before decoding starts.

DECODED SIDE16,384 px

Maximum width or height for a decoded source.

DECODED AREA50 MP

Maximum decoded pixel area.

OUTPUT SIDE8,000 px

Maximum requested width or height.

Privacy boundary

“Browser-local” describes the file path—not a disconnected website.

FormatTailor's static pages still need normal network requests. The distinction is whether the selected image bytes are sent to a FormatTailor processing endpoint.

  1. 01

    Select

    The browser gives the current tab a File. FormatTailor creates local blob URLs for previews.

  2. 02

    Decode

    The tab tries createImageBitmap, then a local <img> path. HEIC/HEIF can load the bundled fallback decoder.

  3. 03

    Render

    Decoded pixels are drawn to a two-dimensional canvas. Size and pixel-count limits are checked in the processing layer.

  4. 04

    Export

    canvas.toBlob() creates the result. The requested MIME type is compared with the Blob's actual type before download.

What this review supports

No FormatTailor file-processing upload path

The reviewed interface passes the selected file into browser APIs and locally loaded JavaScript. Its Astro production build is static and contains no upload handler for these tools.

What it does not promise

No claim that the device is private

The browser, extensions, operating system, security software, hosting network, and eventual destination can still observe activity. Use a trusted device and independently inspect high-risk files.

Expected website traffic

Pages and code still load over the network

HTML, CSS, JavaScript, icons, and a lazily loaded HEIC decoder can create requests. Hosting logs can receive ordinary request information such as IP address, path, time, and user agent.

Reproducible check

Inspect the boundary yourself.

This is a practical check, not a substitute for a professional security audit. Use a disposable, non-sensitive test image.

  1. 1

    Open the browser's developer tools and select the Network panel.

  2. 2

    Reload the chosen tool page, wait for it to settle, and clear the request list.

  3. 3

    Select and process a throwaway JPEG or PNG. For HEIC, expect a JavaScript decoder chunk to load on first use.

  4. 4

    Inspect new requests, including Fetch/XHR and request payloads. The test image bytes should not appear in a request to FormatTailor.

  5. 5

    Repeat after a site release or browser update. Record the page URL, date, browser build, and observed request paths.

Machine-readable data

Use the fields, keep the caveats.

The JSON includes the methodology, safety limits, format rows, status definitions, and source registry. The CSV is a flat format table for spreadsheets. Both carry the same review date.

Suggested citation: “FormatTailor browser image-format capability map, version 1.0.0, reviewed 2026-08-21.” Link to this page so readers also receive the limitations and source notes.

Evidence register

Standards first, implementation notes second.

Format standards establish what a format can represent. Browser support still changes, so the dataset points to maintained compatibility data and labels runtime-dependent paths honestly.

  1. web standard
  2. web standard
  3. compatibility data
    MDN browser-compat-dataOpen Web Docs and MDN contributors
  4. format standard
  5. format standard
  6. format standard
  7. format standard
    AV1 Image File Format (AVIF)Alliance for Open Media
  8. format standard
  9. implementation dependency
    heic2any browser decoder repositoryAlex Corvi and contributors
  10. implementation dependency
    exifr metadata parser repositoryMike Kovarik and contributors
Implementation review: The product-specific rows were checked against src/components/ToolWorkspace.tsx, src/lib/image.ts, src/lib/format.ts, package-lock.json. Dependency repositories document what the included libraries aim to handle; they are not evidence that every source file will succeed.