File Size and Tool Limits
Understand why browser-side tools use file, batch, page, pixel and memory limits.
Updated August 27, 2026EveryFileTool applies browser-safe limits to reduce the chance that a tab freezes or runs out of memory. The exact limit shown inside the tool is authoritative because some specialized tools need stricter or different limits.
Common limits
- Images commonly allow up to 25 MB each and 20 files per batch. Very large pixel dimensions can still be rejected even when the compressed file is small.
- Standard video uploads commonly allow up to 100 MB each, 3 videos, and 200 MB combined. Specialized video tools can show a different limit.
- Audio uploads commonly allow up to 100 MB, and decoded audio is also limited to about 30 minutes plus a browser-memory budget. A small compressed file can still be rejected when its decoded duration, sample rate or channel count would require too much memory.
- General document uploads commonly allow up to 25 MB.
- PDF tools commonly allow a PDF up to 100 MB, with additional page, render, output, or combined-merge limits where needed.
Why a small file can still be too demanding
File size on disk is not the same as memory used while processing. A compressed image expands into pixels, a PDF page expands into a canvas, and video decoding keeps frames and audio data in memory. Device memory, page dimensions, duration, resolution and selected output settings all matter.
What to do
- Choose a smaller file or reduce its dimensions, duration, or page count.
- For a large PDF, split it into smaller documents before processing.
- For images or videos, compress or resize the source first.
- Process fewer files in each batch.
- Close memory-heavy tabs and retry on a device with more available memory.
Limits are stability safeguards, not account or payment quotas.