Browser support and practical limits

Private File Tools targets current versions of Chrome, Edge, Firefox, and Safari on desktop and mobile. A recent desktop browser usually provides the most memory and the broadest media codec support.

Why browser results can differ

Image encoding, canvas size, available memory, and hardware support vary by browser and device. A format accepted on one device may be refused on another, and a large job that works on a desktop may exceed the memory available to a phone.

Media tools

Audio, video, and several GIF tools load an ffmpeg WebAssembly engine of roughly 31 MB on the first run in a tab. Those tools are intended for practical, short files rather than multi-gigabyte production media.

Protective limits

• ffmpeg-backed inputs above 512 MB are refused.
• Decoded image memory is checked before unsafe canvas work.
• PDF raster tools cap document page counts before rendering.
• GIF frame extraction is capped to avoid unbounded output.

A refusal is deliberate: it is safer than freezing the browser or losing work. If a supported file fails, include the browser, operating system, tool URL, file format, and approximate size when reporting the problem. Do not send a private source file.