A PDF upload size limit is the largest file a converter will accept, and it is usually stated in megabytes, pages, or both. Megabytes measure how heavy the file is to send. Pages measure how much work the conversion will take. A short scanned statement can break a megabyte cap, while a long digital one breaks a page cap first.
Why do converters set a PDF upload size limit?
Converters set an upload limit to keep each conversion predictable. Every file has to travel over the network, sit in memory while it is read, and be processed page by page. A cap stops one huge upload from tying up the service for everyone else and keeps the wait short for a normal statement.
There are three costs behind the cap, and each one maps to a different kind of limit:
- Transfer. A 40 MB file takes far longer to send than a 400 KB one, especially on a phone or hotel network. A megabyte cap protects against uploads that would time out halfway.
- Memory. Large page images have to be decoded before anything can be read from them. A megabyte cap also keeps that step bounded.
- Reading time. Every page is read separately, so the work grows with the page count. A page cap keeps the processing time in a range the service can promise.
Some tools state only one of these numbers. Others show both, and a file has to pass both to be accepted. When a converter rejects your statement, the error usually says which limit you hit. Read that line before you change anything, because the fix for a heavy file is different from the fix for a long one.
Megabytes versus pages in a PDF upload limit
Megabytes and pages measure different things, and a statement can pass one while failing the other. Check the megabyte size first if the file is a scan or a phone photo, because images are heavy. Check the page count first if the file is a long digital download, because text-based pages are light but numerous.
A digital statement, the PDF your bank lets you download, stores its text as characters. A page of transactions in that form is often a few tens of kilobytes. A scanned statement stores each page as a picture, and one picture at a high resolution can weigh more than a whole year of digital statements.
The examples below are illustrative, not measurements of any real bank's files:
| Example file | Pages | Size | Limit it is likely to hit | Fix |
|---|---|---|---|---|
| Digital checking statement, one month | 4 | 0.3 MB | Neither | Upload as is |
| Digital statement, twelve months combined | 60 | 3 MB | Page cap | Split by month or quarter |
| Phone scan of a paper statement | 5 | 28 MB | Megabyte cap | Rescan at a sensible resolution |
| Fuel card statement with every fill-up listed | 35 | 2 MB | Page cap on smaller plans | Split by billing period |
The last row is common for fleets. A fuel card statement converted to Excel can run to dozens of pages because each vehicle and each fill-up gets its own line, so it reaches a page cap well before it gets heavy.
FastBankConvert's early pricing is stated in pages: the paid plans on the FastBankConvert homepage list monthly page allowances, and the homepage notes that plans and limits may change before launch.
What makes a statement PDF heavier than its page count?
A statement PDF is heavier than its page count suggests when the pages hold pictures instead of text. Scans, phone photos, embedded logos saved at full resolution, and fonts packed into the file all add weight. A five-page file that weighs 20 MB or more is almost always storing every page as an image.
Look for these causes:
- Scanned pages. A scanner set to 600 dpi in full colour produces a very large image per page. Statements are black text on white paper and rarely need colour.
- Photos of pages. Phone cameras save large images, and a PDF made from photos keeps them at that size.
- A printed-then-scanned copy. Someone printed a digital statement and scanned it back in. The file lost its text and gained weight.
- Many statements merged. Combining a year of files into one adds the pages together, and each one keeps its own fonts and images.
If the file came straight from your bank's website and is still heavy, the bank may have embedded large images such as marketing inserts. Removing those pages is often enough.
Bringing an over-limit statement PDF under the upload cap
Bring an over-limit statement under the cap by matching the fix to the limit you hit. For a megabyte cap, reduce image weight: download the digital original, or rescan in greyscale at a moderate resolution. For a page cap, split the file into smaller date ranges and upload each part on its own.
When the file is too heavy
- Ask for the bank's downloadable PDF instead of a scan. It is smaller and reads more reliably.
- If only paper exists, rescan in greyscale or black and white at around 300 dpi.
- Delete pages that hold no transactions, such as terms, ads and blank backs.
- Compress only as a last step, and use a method that keeps the text layer. Compressing a PDF without losing its text covers which settings do that.
When the file has too many pages
Split the file along statement boundaries, one month or one quarter per part, so each part starts with an opening balance and ends with a closing balance. A split in the middle of a month leaves a part whose balances cannot be checked on their own.
Smaller parts also convert faster. The fastest way to convert a PDF to Excel explains why a clean digital file of a few pages is the quickest case for any converter.
Shrinking tricks that ruin an over-limit statement PDF
Some ways of shrinking a PDF get it under the cap but destroy what the converter needs. Printing to an image PDF, compressing to a very low resolution, and cropping away the header all make the file smaller while making the numbers harder or impossible to read. A file that uploads but converts badly costs more time than a split.
Avoid these:
- "Print to PDF" as an image. Some print drivers flatten each page into a picture. The text layer disappears, so a digital statement turns into a scan.
- Aggressive compression. Online compressors with a "maximum" setting can blur small digits until a 3 looks like an 8. The balance check may catch the error, but only after a wasted run.
- Cropping off the header. The header holds the account details and the statement period, which are needed to place dates in the right year.
- Removing pages inside a month. Dropping a page of transactions to save space makes the closing balance impossible to reach.
The safe rule is short: remove whole pages that hold no transactions, keep every page that does, and split along months rather than squeezing the images.