Image PDF Tools
Browser and format compatibility
The web capabilities required by local image and PDF workflows, with limits that must be checked on the visitor's actual device.
This matrix describes implementation requirements, not a claim that every browser/version combination has been directly tested.
| Capability | Required browser support | Known limitation |
|---|---|---|
| Local image jobs | JavaScript, Worker, Canvas, Blob downloads, typed arrays, and enough decoded-pixel memory | Color management, maximum canvas size, codecs, and memory ceilings vary by browser and device. |
| AVIF and WebP output | Lazy-loaded bundled codecs and WebAssembly support | Encoding is CPU- and memory-intensive; older destination applications may not open the result. |
| HEIC/HEIF input | Dedicated separately loaded local decoder | Exports the supported primary still path, not every auxiliary image or container feature. |
| PDF page previews | PDF.js, local canvas rendering, Worker support, and bounded page/render budgets | A preview identifies a page but does not prove preservation of forms, signatures, links, attachments, or accessibility. |
| PDF page-object output | Local PDF parsing and pdf-lib-compatible page copying | Document-level interactive structures can be omitted or invalidated when a new PDF is written. |
| Downloads and ZIP | Blob/Object URL download support and sufficient memory for final assembly | Managed browsers, mobile systems, private mode, and extensions may rename, block, or terminate downloads. |
How to verify
Use a current browser, process a non-sensitive representative fixture, open the saved result in the destination application, and disclose Firefox or Safari behavior as unverified unless that exact path is directly exercised.