Browser compatibility
Local processing means your browser is the engine. Most tools work in every modern browser; media tools inherit your browser's codec support, which differs. Here is the honest map.
Baseline support
| Category | Chrome / Edge ≥ 110 | Firefox ≥ 115 | Safari ≥ 16.4 |
|---|---|---|---|
| Images and screenshots | Full | Full | Full |
| PDFs | Full | Full | Full |
| Spreadsheets | Full | Full | Full |
| Video and audio | Full | Full | Partial — see notes below |
Versions listed are practical baselines, not hard cutoffs: older browsers may work for lighter tools, and each tool checks the capabilities it needs at runtime and says so when one is missing, rather than failing silently.
Containers versus codecs — why media support differs
A video file has two layers: the container (MP4, WebM, MOV — the box) and the codecs (H.264, HEVC, VP9, AAC, Opus — how the picture and sound inside the box are encoded). A browser may open the box but not know how to decode what's inside. That is why “does my MOV file work?” has no universal answer: it depends on which codec is inside and which decoders your browser and operating system ship.
- Input: our media tools can process anything your browser can play. H.264 MP4 works essentially everywhere; HEVC (common in iPhone MOV files) decodes on Safari and on Chrome/Edge where the operating system provides it; WebM plays in all modern browsers, with Safari support arriving in recent versions.
- Output: exports use the encoder your browser exposes via MediaRecorder, which produces WebM (VP8/VP9) on Chrome, Edge, and Firefox. Safari's MediaRecorder historically produces MP4/H.264 instead — the tools detect what your browser offers and label the output format before you export.
Notes by browser
- Chrome and Edge: the most complete platform for every category, including media export.
- Firefox: full support across categories; media export is WebM.
- Safari: image, PDF, and spreadsheet tools are fully supported. For media, input support is strong for Apple-ecosystem formats (including HEVC), while export format and WebM handling vary by version. Tools state the exact capability they detected on your device before you start a long export.
- Mobile browsers: everything runs, within the memory limits of the device. Very large files are the practical constraint, and tools fail safely with an explanation rather than crashing the tab when a file is too large to decode.
Our promise about honesty here
Capability differences are facts of the platform, not something to paper over with marketing. Wherever a tool depends on a feature your browser lacks, the tool tells you what is missing and what your options are — a different browser, a smaller file, or a different output format.