Check the saved file's actual byte size against the receiving system's instructions. Do not estimate acceptance from page count or a tool's "high compression" label. The upload-size checker measures selected files on your device and compares their combined size with a decimal MB limit you enter. It does not modify or upload files.
Read the receiving system's limit first
Determine whether the limit applies to each file, a group of attachments, or an entire submission. Those are different constraints. A portal might also impose format, page-count, or naming rules; our checker does not validate those. If instructions only say "MB" without defining units and your file is close to the boundary, leave headroom and confirm with the recipient rather than relying on a borderline calculation.
This tool uses decimal units: one MB equals 1,000,000 bytes. A MiB is 1,048,576 bytes. A file described as five megabytes by one display may be labeled differently by another if the unit convention differs. The underlying byte count is the stable comparison. We use MB consistently here and do not silently switch to binary units.
Calculate the required reduction
If the selected files total S bytes and your entered limit is L bytes, the reduction needed when S is greater than L is (1 − L ÷ S) × 100 percent. If S is already at or below L, the required reduction is zero. This calculation describes a target; it does not predict whether any compressor can reach that target while keeping the content usable.
For an illustrative example, suppose a combined file is 8,000,000 bytes and the destination limit is 5,000,000 bytes. The required reduction is (1 − 5,000,000 ÷ 8,000,000) × 100 = 37.5 percent. That is a reduction of 3,000,000 bytes. A tool's quality slider at 62.5 percent would not necessarily achieve the remaining 62.5 percent of the original bytes.
| Illustrative file size | Entered limit | Required reduction |
|---|---|---|
| --- | --- | --- |
| 8 MB | 5 MB | 37.5% |
| 12 MB | 3 MB | 75% |
| 4 MB | 5 MB | 0% |
Choose a response that preserves the task
If images dominate a document, a scan-optimization workflow may help. If the PDF was exported from a document editor, inspect that editor's export options before converting pages into pictures. If the recipient permits separate attachments, that may avoid altering image quality, but do not split a required single packet without permission.
Removing unneeded pages can reduce content and size, but "unneeded" must come from the actual submission instructions. Do not remove legal notices, reverse sides, appendices, or blank pages that the recipient explicitly requires. A file that fits the limit but lacks a required page is not a successful submission.
Recheck the final artifact
Run the size check on the exact file you intend to submit, after all merging, conversion, or compression is complete. Adding a cover sheet afterward changes the file and invalidates the earlier measurement. Use a recognizable final filename so that you do not accidentally upload a previous draft.
If the portal rejects a file that is below the size limit, stop treating every error as a compression problem. Check the permitted extension, password restrictions, maximum page count, and whether the service itself is reporting a temporary error. The visible error message is more useful evidence than repeatedly degrading the same document.
Separate measurements from estimates
Selecting several source files gives their current combined byte count. It is useful for planning a packet, but it is not a promise about the bytes of a later merged result. A PDF writer may introduce new structures, preserve existing objects, or rewrite parts of the document. Only the saved final artifact tells you the final size.
When comparing two versions, give them distinct filenames and check each individually. Record the actual bytes or decimal MB, the change you made, and whether readability remained acceptable. If a lower-quality setting makes almost no useful difference, return to the original and reconsider the workflow rather than repeatedly encoding the same reduced output.
For example, an illustrative original of 6 MB and a revised file of 4.8 MB differ by 1.2 MB. Dividing 1.2 by 6 gives a 20 percent reduction. That comparison is separate from the reduction required to meet a limit. If your actual destination limit were 4 MB, this revised output would still be too large despite the improvement. Keep the target comparison and the before-versus-after comparison distinct.
If a submission contains multiple independently limited attachments, repeat the check for each one. A combined total below an overall cap does not prove that every individual file meets its own cap. Conversely, files that each fit a per-file limit may still exceed an overall request limit when grouped together. Read the instructions at both levels before changing any document.
FAQ
Does selecting several files simulate a merged PDF?
No. It adds their current byte sizes. A merger may add or rewrite structures, so measure the merged output separately.
Does this checker open or validate a PDF?
No. It uses file sizes supplied by the browser. It does not confirm that the file is a valid PDF or that its contents are safe.
Does a result below the limit guarantee acceptance?
No. It only establishes the comparison with the limit you entered. The recipient's other requirements still apply.
Related guides
Read the workflow guide, image conversion steps, and readability checks after compression.
Sources
- Folio Bench implementation: decimal-unit conversion, file-size measurement, and the formula above are documented directly from the local size-checker code. No portal-specific limits are asserted.