When your browser crashes with a large PDF, it has usually run out of memory while drawing the pages. Close other tabs and any PDF preview, switch off extensions you do not need, and restart the browser. To convert the file, you rarely need to open it at all: pick it from your folders and upload it directly.
Why does a browser crash with a large PDF?
A browser crashes with a large PDF because drawing each page takes memory, and a big file can ask for more than the tab or device can give. Scans are the worst case, since every page is a big image. When the tab cannot get more memory, it freezes or shows an error page.
What counts as large for a browser
Page count and page weight both matter. A 300-page text statement can be heavy because the viewer prepares many pages as you scroll. A 20-page scan at high resolution can be just as heavy, because each image is big. Older laptops, low-memory Chromebooks and phones reach the limit sooner.
Why it sometimes works on the second try
After a restart, the browser has more free memory, so the same file may open. That is a hint the problem is memory, not the file.
Closing tabs and preview windows before opening a large PDF
Closing tabs and preview windows is the quickest way to free memory before opening a large PDF. Video, maps and web apps hold a lot of it. Google's help page on fixing Chrome when it crashes notes that your computer may have run out of memory and suggests closing every tab except the one showing the error.
What to shut first
- Tabs playing video or audio.
- Web apps that stay live, such as email, chat or dashboards.
- Any earlier tab where you opened the same PDF.
- Other programs on the computer that use a lot of memory.
Download instead of preview
Many links to a PDF open it in the browser's built-in viewer. Saving the file instead, with the browser's download option, avoids drawing the pages at all. Some PDFs are saved for fast web view, which lets a browser show the first page before the rest arrives; the guide to fast web view PDFs explains what that setting does and when it helps.
Browser extensions that make large PDF crashes worse
Browser extensions can make large PDF crashes worse because some of them run on every page you open, including the PDF viewer. Ad blockers, page translators, grammar checkers and PDF add-ons each take memory of their own. Google's crash help page notes that one extension could be causing the problem.
To find it, that page suggests uninstalling every extension and adding them back one at a time.
Finding the culprit
Open the browser's extensions page and switch everything off. Try the PDF again. If it opens, switch extensions back on one at a time until the crash returns. A private or incognito window is a faster test, since most browsers run it with extensions off by default.
Hardware acceleration
The same help page also suggests turning off "Use hardware acceleration when available" in Chrome's System settings, then restarting Chrome, for crashes linked to graphics. Try it if crashes continue with extensions off.
Uploading a large PDF without opening it in the browser
Uploading a large PDF does not require opening it in the browser. A file upload button or a drag-and-drop area reads the file from your folders and sends it, without drawing a single page. This sidesteps the memory problem completely, so it is the most reliable route for a file that crashes the viewer.
Steps that avoid the viewer
- Save the PDF to your computer or phone rather than opening it in a tab.
- Restart the browser so it starts with free memory.
- Open only the converter's page.
- Drag the file from your folder onto the page, or use its file picker.
- Wait for the upload to finish before opening anything else.
FastBankConvert, which is getting ready to open, is built for exactly this: you drop a statement PDF onto the page or pick it from your files, and download the result. Get started to hear when trial conversions open.
After the conversion
A long statement produces a long spreadsheet. The guide to Excel shortcuts for converted data helps you move around it quickly, and if rows come out in an unexpected order, read about rows out of order after PDF conversion.
Is the large PDF itself damaged, not the browser?
The large PDF itself may be damaged when it crashes every browser and every reader on every device. A file cut short during download, or saved badly by the app that made it, can make viewers fail in ways that look like memory problems. Testing in a second program tells the two apart quickly.
A quick test
- Open the file in a desktop PDF reader instead of the browser.
- Check the file size against what you expected. A file far smaller than similar ones may be truncated.
- Download it again from the original source.
If the desktop reader opens it fine, the browser is the limit and the steps above apply. If nothing opens it, get a fresh copy from the bank or sender before trying to convert it.