Your scanned archive is 800MB. You need to delete 40 of its 600 pages. Most online tools choke on uploads that size — and you really don't want to wait 20 minutes for an upload before discovering they cap at 100MB anyway.
Flint handles large files in your browser, no upload required.
Why local processing wins for big files
Cloud-based tools have to upload your file, process it on their server, and send it back. For 800MB that's 30+ minutes of network I/O even on a fast connection. Flint loads the file directly from your disk into your browser memory. No upload step. Processing starts immediately.
Memory considerations
Browsers can hold several hundred MB comfortably. For files past 500MB, close other tabs and give Flint room to work. If your machine has 8GB RAM or more, even gigabyte-sized PDFs work. Slower machines may struggle past 300MB — try splitting into smaller chunks first.
Delete then optionally compress
After deleting your 40 pages, the output file is still big (because the surviving 560 pages are still scanned at high DPI). Run the deleted result through compress PDF for a much smaller file. Two operations, one local. No upload either time.
Splitting first if memory is tight
If Flint reports an out-of-memory issue, split your big PDF into halves first. Delete pages from each half. Merge the cleaned halves back. More operations but each on a smaller chunk.
FAQ
Maximum file size for Flint?
No hard cap. Browser memory is the limit. Most users handle up to 1GB; some go higher with enough RAM.
Will saving take long?
Save speed depends on file size. A 600MB output takes a few seconds to write locally — still faster than uploading.
Better to delete or to split for big files?
Delete if you know what to remove. Split if you want to extract specific pages and discard the rest.
Are very large PDFs slow to render?
Initial thumbnail generation takes longer. After that, interactions are smooth.
Local processing, no upload. Delete from large PDFs.