At a glance
There is no reliable universal conversion from megabytes to PDF pages. Images, fonts, compression, attachments and object structure affect bytes independently of page count. Use actual verified pages for document work and bytes for download, storage and processing allowances.
The examples show why an assumed bytes-per-page ratio is unsafe.
| File | Possible content | What remains unknown |
|---|---|---|
| One large page | High-resolution scanned drawing | Page count from bytes alone |
| Many small pages | Mostly text with shared resources | Complexity from bytes alone |
| Equal-size PDFs | Different image/compression choices | Whether page counts match |
| Tiny download | HTML error instead of a PDF | Whether it contains any PDF pages |
Scroll sideways to see all columns. Use arrow keys when the table is focused.
Use the right unit for the question
File bytes describe transfer or storage volume. Pages describe a document’s page tree. URL counts describe download locations, while unique-file groups describe retrieved byte identities. These measures can be related in one ledger without being interchangeable.
| Measure | Good use | Poor inference |
|---|---|---|
| Bytes / MB / GB | Transfer and storage planning | Accessibility or page count |
| Verified pages | Page-based work scope | Document importance |
| PDF URLs | Public link maintenance | Unique sources without identity evidence |
| Sampled page profile | Nominate manual review | Full-document complexity or price |
Scroll sideways to see all columns. Use arrow keys when the table is focused.
Interpret download allowances accurately
Check the unit convention used by the service. Decimal MB is one million bytes; binary MiB is 1,048,576 bytes. A display rounded to one decimal place is a presentation, not a new exact measurement.
A collection can reach a transfer allowance with few image-heavy PDFs or fit many text PDFs inside it. Per-file limits and parser boundaries are additional constraints. Do not predict the number of files a website inventory will finish using average file size alone.
- Inspect saved per-file and total transfer allowances.
- Keep observed bytes and verified counts in separate columns.
- Retain interrupted-transfer accounting notes where the service reserves an allowance.
Estimate from actual sources
For an initial project, retrieve and count an authorized representative set, then keep the sampling boundary explicit. Do not extrapolate a precise total from one large file or from a visually simple first page.
For a confirmed collection, use its count ledger and document-owner decisions. Unknown counts and incomplete discovery are separate scope gaps. Compression may reduce transfer size but does not prove that a file’s semantics or reader experience improved.
Sources and scope
Methods, worksheets and illustrative examples are DocAccessible editorial contributions. These references support the technical or product details described above. W3C techniques are informative guidance; they are not a certification scheme.
- QPDF: PDF inspection and exit status
Structural inspection, page-count options and warning versus error outcomes.
- DocAccessible PDF inventory
The counting workflow, report options and purchase boundary.
Written by the DocAccessible team under our editorial policy. Suggest a correction if a source or product detail needs updating.
See the evidence in a working example
Explore the public sample inventory report to try its table, full-screen view and missing-count reasons. The downloadable counting fixture check records what the local counter returned for seven self-authored inputs, with hashes and explicit limits.