BASALT · JOURNAL
How large a PDF can you actually open on a Mac
The question is usually asked the wrong way round. People ask how many pages an application can open, when the number that decides the answer is how many bytes it decides to hold in memory at once.
A 2,000 page text document is often under a megabyte. The same 2,000 pages scanned at 300 DPI is several hundred megabytes, because each page is now a photograph rather than a line of text. Page count and file size are close to unrelated, and only one of them is a load on your machine.
What actually costs memory
Three things, in increasing order of severity.
Parsing the file structure costs almost nothing. The cross reference table and page tree are small, even for a document with tens of thousands of objects.
Rendering a page costs memory in proportion to the page, not the document. A letter sized page at screen resolution is a few megabytes of bitmap regardless of whether it came from a five page file or a five thousand page one.
Holding the file costs memory in proportion to the file, and this is where applications fail. An application that reads a document into a buffer before doing anything needs as much memory as the document is large, plus room to work. On a 2 GB production that is where the beachball comes from.
The measured numbers
On a 273 MB, 1,000 page scanned PDF, opening the document and rendering the first page took 0.06 seconds, with peak resident memory of 89 MB. Rendering page 500 of the same document took the same 0.06 seconds.
Both halves of that matter. Memory well under the file size means the file was never read into a buffer. Page 500 costing the same as page 1 means pages are being rendered on demand rather than eagerly, so the cost of opening does not grow with the length of the document.
The machine was an Apple M1 Pro with 16 GB, running under Rosetta, so a native build should do better rather than worse. This is one run on one machine, not a regression suite.
What to check in whatever you use
Open your largest document and watch Activity Monitor. If the memory figure for the application climbs to somewhere near the size of the file, the application is holding the document rather than reading through it, and your ceiling is your available RAM.
Then jump to the last page. If that takes noticeably longer than the first page did, pages are being loaded as you go, which is fine. If the document took a long time to open but every page is instant afterwards, it was loaded up front, which is the pattern that fails on large files.
Frequently asked questions
How large a PDF can a Mac open?
It depends on the application rather than the Mac. An application that reads the whole file into memory is limited by available RAM, so a 2 GB document needs at least 2 GB free plus working space. An application that reads through the file in chunks and renders pages on demand is limited by disk space instead, which is usually far more generous.
Does the number of pages in a PDF affect performance?
Less than people expect. A 2,000 page text document can be under a megabyte, while 2,000 scanned pages can be several hundred megabytes. File size drives memory use and page count mostly does not, so a short scanned document can be much heavier than a long text one.
Why does my PDF take so long to open?
Usually because the application is reading the entire file before showing you anything, or because it is rendering every page rather than the one you are looking at. A useful test is whether the last page opens as quickly as the first: if it does, pages are being rendered on demand and the initial delay was the file being loaded.
How much memory should a PDF application use?
For viewing, roughly the size of the pages being displayed, not the size of the document. If memory use tracks file size, the whole document is being held at once.
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.