A PDF conversion timed out because the job needed more time than the converter allows for one file. Long page counts, scanned pages that need text recognition, and oversized images on a slow upload are the usual causes. Give the next attempt less work: send fewer pages, a smaller file, or a digital copy instead of a scan.
Why does a PDF conversion time out?
A timeout is a deadline. Online converters stop any single job that runs past a set time, so one heavy file cannot hold up the service for everyone else. When your PDF conversion timed out, the tool did not necessarily fail to read the file. It ran out of the time it was given before it could finish.
The deadline can come from more than one place. Your browser may give up waiting for a reply. The converter's server may cap how long it spends on one document. A network proxy at work can cut long connections. Each of these produces a similar message, often "timed out", "request took too long" or simply a spinner that never ends.
Most tools do not publish their exact limit, and limits vary between free and paid tiers. You rarely need the number. What you need is to know which part of the job was slow, because that decides whether to cut pages, shrink images or change the connection. The next section shows how to tell.
Time of day can matter too. A shared online service is busier at some hours than others, and a job that sits close to the deadline may finish at a quiet moment and fail at a busy one. That kind of timeout comes and goes. A timeout that repeats every time, on every network, is about the file.
Is the timeout in the upload or in the PDF conversion itself?
Look at where the progress stopped. If the upload bar never reached the end, the file did not finish arriving, and the problem is size or connection. If the upload completed and the job stalled while "processing" or "reading pages", the conversion itself ran out of time, and the problem is the amount of work inside the file.
Use this table to match what you saw to a fix. The rows describe typical patterns, not rules from any one tool.
| Where it stopped (example) | Likely cause | Change to make |
|---|---|---|
| Upload bar stuck partway | Large file on a slow or unstable connection | Shrink the file or switch to a faster network |
| Upload done, stuck on the first pages | Scanned pages needing OCR | Get a digital copy, or send fewer pages at once |
| Upload done, stuck near the end | Very long file | Split it into parts |
| Fails at the same page every time | One damaged or oversized page | Remove or replace that page |
| Fails only on a work network | Proxy closing long connections | Try another network |
For the upload side, uploading a PDF on a slow connection covers practical fixes such as shrinking the file first and pausing other uploads and downloads. The rest of this guide deals with the work inside the file.
Page count and the conversion time limit
A digital PDF takes time roughly in proportion to its pages, because each page is read and turned into rows. A year of statements combined into one file can be ten or twenty times the work of a single month, and that is where a conversion time limit tends to bite. Sending fewer pages per job is the simplest fix.
There is no universal safe page count. It depends on the tool and on how dense each page is. A practical approach is to work down from the whole file:
- Try the full file once.
- If it times out, split it in half and try one half.
- If that half finishes, convert the other half the same way.
- If it still times out, halve again until each piece finishes comfortably.
Monthly statements make natural pieces, since each month starts and ends on a balance you can check. Combined annual files are convenient to store, but they are a poor shape for conversion. Splitting by month also means a single failure costs you one month of rework, not a year.
Some files are long because of pages you do not need. Cover letters, terms and conditions, marketing inserts and blank backs of scanned sheets all count against the limit. Removing them before conversion saves time and gives a cleaner result.
Dense pages cost more than sparse ones. A business account with sixty transactions on every page asks far more of a converter than a savings account with three lines a month, even at the same page count. If your file is busy, expect to use smaller pieces than you would for a quiet account, and do not judge a tool by how it handled a lighter file last time.
OCR work on scanned pages behind a timeout
Optical character recognition (OCR) is the step that reads text from a page image. A scanned PDF has no real text, so every page goes through OCR before any rows can be built. That is many times the work of reading a digital page, which is why a 30-page scan can time out when a 30-page bank download finishes easily.
Several properties of a scan push the OCR time up:
- High resolution. Scanning far above what text needs multiplies the pixels to examine.
- Colour. A colour scan of a black-and-white statement is heavier than a greyscale one.
- Poor image quality. Skewed pages, shadows and speckles make recognition slower.
- Phone photos. Each photo needs its page edges found and straightened first.
The fastest fix is to avoid OCR altogether. Most banks let you download past statements as digital PDFs from online banking, and a digital copy has none of these costs. When you only have paper, rescan at a moderate resolution in greyscale and send the pages in smaller groups. OCR pages per minute explains how recognition speed varies, so you can size those groups sensibly.
Splitting a timed-out PDF into pieces that finish
Splitting a PDF means saving a subset of its pages as a new file. Any PDF editor can do it, and so can free command-line tools. qpdf is one of them: it copies chosen pages into a new file without re-rendering them, so text stays text and the pieces are no worse than the original.
The qpdf command-line documentation describes two options that fit this job. Here is a step list, with an example file name you should replace with your own:
- Check the page count of the original in your PDF viewer. Suppose
statements-2025.pdfhas 60 pages. - Split into fixed groups.
qpdf --split-pages=10 statements-2025.pdf part.pdfwrites six files of 10 pages each. The documentation shows the output files named by page range, such aspart-01-10.pdf. - Or pick one range.
qpdf statements-2025.pdf --pages . 11-20 -- part-b.pdfsaves pages 11 to 20 only. The dot stands for the input file, andzcan stand for the last page, as in41-z. - Convert each piece separately and note which ones finish.
- Stitch the results back into one sheet in the original page order.
- Check the joins. Where one piece ends and the next begins, confirm the closing balance of the first equals the opening balance of the second.
If you prefer not to use a command line, most desktop PDF readers offer "print to PDF" with a page range. That works, but on some systems it re-renders the pages, so search the result for a word to confirm the text layer survived.
Split on statement boundaries where you can. A cut in the middle of a month leaves a balance that you can only check by putting the two halves back together, while a cut between months gives each piece its own opening and closing balance.
Retrying a timed-out PDF conversion unchanged
Pressing retry on a file that timed out usually gives the same result, because the file still needs the same amount of work. A retry helps only when the cause was temporary, such as a dropped connection or a busy moment on the server. If the second attempt stops in the same place, change the file before trying again.
A few habits make repeated timeouts more likely:
- Retrying again and again. Each attempt costs the same time and teaches you nothing new. Two failures in the same spot is a signal, not bad luck.
- Making the file bigger. Re-saving a PDF through some tools adds images or embeds fonts again, so the "fixed" copy is heavier than the original.
- Compressing a scan too hard. A smaller upload that OCR can barely read may finish faster but return wrong digits.
- Converting pages you do not need. If you only need a few transactions, sending a whole year is wasted work. Extracting only the fields you need from a PDF shows how to aim at the data instead of every page.
When a file finally finishes after a struggle, check the output more carefully than usual. Count the transactions on one page against the rows you got back, and confirm the closing balance. FastBankConvert is designed to show a timer while it works and to warn you before the download if a statement's balances do not add up, which makes a half-read file easy to spot. You can see the sample conversion on the homepage before trying your own.