BASALT · JOURNAL
What to do when a PDF is too large to open
A PDF that will not open is usually a healthy file meeting an application that made an assumption about size. Before treating the document as damaged, it is worth working out which of the two is failing.
Check the file first
Look at the size on disk. Anything over a few hundred megabytes is almost certainly a scanned document, and scanned documents are where size problems live.
Then confirm the file is structurally sound. qpdf --check file.pdf reads the structure and reports damage without rendering anything, so it answers the question quickly even on a very large document. If qpdf reports the file is fine, the file is fine, and the application is the problem.
Tell the two failure modes apart
An application that runs out of memory usually beachballs, then either quits or comes back with a vague error. Watch its memory in Activity Monitor while it opens: a figure climbing steadily towards the size of the file means the whole document is being read in, and the ceiling is your available RAM.
An application that is merely slow will show you the first page eventually. That is not a failure, just an eager renderer.
What usually works
Split the document before opening it. qpdf --split-pages=100 big.pdf part.pdf writes hundred page chunks without needing to render anything, and it works on files far larger than most editors will open.
Close other applications. This sounds trivial and is often the whole fix, because the failure is a memory ceiling rather than a document defect.
Use an application that reads through the file rather than loading it. This is the real solution, and it is worth checking for directly: open your largest document and see whether memory tracks the file size.
What rarely works
Converting to another format and back. This usually means rendering every page, which is more expensive than opening the file, and it destroys text, structure and any embedded data in the process.
Compressing the file first. Reasonable in principle, but most compression tools have to open the document to compress it, so they hit the same ceiling.
A note on scanned productions
If the document came from a scanner or a discovery vendor, expect several hundred megabytes for a thousand pages and expect no extractable text. Both are normal. A tool that can open the file but cannot search it has not failed; the document simply has no text layer, and OCR is a separate step that adds one.
Frequently asked questions
Why will my large PDF not open?
Most often because the application reads the entire file into memory before displaying anything, and the file is larger than the memory available. Check with qpdf --check file.pdf, which reads the structure without rendering: if it reports no problems, the document is sound and the application is the limitation.
How do I open a PDF that is too large?
Split it first with a tool that works on the file structure rather than the rendered pages, such as qpdf --split-pages=100 big.pdf part.pdf. That runs on files far larger than most editors will open. Closing other applications also helps, since the failure is usually a memory ceiling.
Is a 1 GB PDF corrupt?
Not necessarily. A thousand pages scanned in colour at 300 DPI reaches that size legitimately. Verify with qpdf --check before assuming damage.
Does splitting a PDF lose quality?
No, when the split is done at the file structure level. Pages are copied as they are, with no decoding or re-encoding, so the output is byte for byte the same content. Quality loss comes from converting or rasterising, not from splitting.
Doing it in Basalt
Basalt is a native macOS PDF toolkit with eighteen tools in one window. It opens large documents without loading them into memory, renders pages on demand, and copies files into its engine in fixed-size chunks, so peak memory follows the chunk size rather than the file size. Redaction destroys content rather than covering it, and an independent verifier re-opens every written file to prove the material is gone before the file is saved. A one time $29 licence covers up to three Macs, it is free for the first 24 hours, and the engine holds no network entitlement at all, which macOS enforces at the code-signature level. Download it at basaltformac.com.
Redaction that proves itself
Basalt destroys the content you mark, then re-opens the file it wrote and proves the content is gone before it saves anything. Your documents never leave your Mac.