No—the file is not uploaded when you compress a PDF to size; PDF reading, image encoding, measurement, and verification stay in your browser.
Selecting a PDF through your browser’s file picker gives the page access to the local document without sending the document to a server. With Compress PDF to Size, that local document is used to create a candidate PDF, check its actual byte size, and confirm its page count before a download is offered.
This answer concerns the PDF file itself. It means the document is processed locally rather than being transferred to an upload service or included in a server-side compression job.
What stays on your device
The local workflow keeps the main stages together: the browser reads the PDF, eligible JPG images are recompressed, each candidate PDF is saved, its actual file size is measured, and a passing candidate is reopened for verification. The tool compares the bytes of the real saved PDF with your target instead of estimating the result from the original file size.
That distinction matters for privacy. A PDF can contain pages, text, images, forms, and attachments, so an upload would expose the complete document. Here, the file-reading, image-encoding, size-measurement, and verification stages remain in the browser.
Technically, browser-based PDF and image libraries support this kind of local processing. The Mozilla PDF.js API provides browser-based PDF handling, while the WHATWG HTML Canvas toBlob method defines image encoding in the browser. The tool also uses PDF.js to reopen a passing candidate and verify that its page count matches the original.
| Item | Verified behavior |
|---|---|
| Processing location | Local in the browser; the source PDF is not uploaded. |
| Source input | One local PDF, up to 25 MB. |
| Target range | 0.1–25 MB, with a target smaller than the source file. |
| Eligible images | Unmasked DCTDecode DeviceRGB or DeviceGray JPG images without decode parameters. |
| Job limits | Up to 80 eligible images and 100 megapixels across the images decoded. |
| Download condition | The actual saved PDF is at or below the target, and its page count is verified. |
These are processing boundaries rather than promises that every PDF can be reduced to every requested size. The next sections explain what can change and why some files may not produce a result.
What the compressor actually changes
Compress PDF to Size is a target-aware JPG recompression tool, not a general-purpose optimizer for every object inside a PDF. It looks for embedded JPG image streams that can be safely replaced. That makes image-heavy and scanned PDFs more relevant than documents whose size comes mainly from text, vectors, or unsupported image formats.
An eligible image must be an unmasked DCTDecode image using a DeviceRGB or DeviceGray color space, and it cannot contain decode parameters. Unsupported image objects are preserved rather than converted. The tool also leaves an individual image untouched when a newly encoded JPG would be larger than its original stream.
To avoid endless browser work, the tool uses a fixed sequence of JPEG quality and maximum-dimension profiles. It moves from gentler settings, such as 0.70 quality with a 1400-pixel longest side, through progressively lower-quality and smaller profiles, ending at 0.30 quality with a 600-pixel longest side. It stops after that bounded sequence rather than continuing indefinitely to force a result.
The tool does not rasterize whole pages. Page structure, selectable text, links, forms, vectors, and unsupported objects remain untouched, but that does not make the process a general lossless optimization. Eligible JPG images can be recompressed with reduced quality or dimensions, so visual details may change. Keep the original and inspect the downloaded result when document fidelity is important.
Set a target and download a verified PDF
Use the local Compress PDF to Size tool when you have a genuine file-size limit and your PDF contains JPG images that can be recompressed.
- Choose one local PDF. Open the file from your device and confirm that it is no larger than 25 MB. The tool accepts one source PDF per job.
- Enter the required target in MB. The target must be between 0.1 MB and 25 MB and smaller than the original file. Use the maximum size accepted by the service or portal that will receive your PDF.
- Select “Compress to target size.” The local process begins with the eligible JPG images in the selected document.
- Let the bounded profiles run. The tool creates candidate PDFs, compares each candidate’s actual saved byte length with your target, and checks a passing candidate by reopening it and comparing its page count with the original.
- Download only after verification. A download option appears only when the saved PDF is at or below the target you entered. If no candidate qualifies, no result is offered.
The target acts as a maximum size, not a requirement to produce a file with precisely the same byte count. A smaller saved PDF still qualifies because the tool accepts an actual result at or below the stated limit.
Keep the source file as your backup and save a successful result under a separate name. That makes it possible to compare the two documents before replacing the original.
Limits that can prevent a result
The most important limitation is that safe JPG recompression may not provide enough savings. A text-only PDF may contain no eligible JPG stream to reduce. A vector-heavy PDF may derive most of its size from content that the tool deliberately leaves untouched. A file dominated by unsupported images may also remain too large because those objects are preserved.
If every candidate produced by the bounded profile sequence is still above the requested size, the tool creates no download and explains that the target cannot be reached safely. This outcome means the method was not strong enough for that document and target, not that the PDF was uploaded or replaced with an unverified approximation.
The tool does not keep trying until it reaches any target you can imagine. Its fixed sequence is designed to avoid unbounded browser work and misleading output. If you receive no result, review the document type, target, and supported limits before changing the request. The guide to troubleshooting PDF compression to a target size provides a structured way to check those points.
How different PDF contents affect compression
The document’s contents determine whether JPG recompression has enough eligible image data to work with. The table describes the expected relationship; the exact outcome for your file and target is determined by the tool’s real saved-byte measurements.
| PDF type | Likely outcome |
|---|---|
| Scanned, JPG-heavy PDF | Most likely to benefit because page images can be recompressed; a scan may reach a much lower target. |
| Mixed PDF with JPG images | Eligible JPG streams may shrink while text, vectors, forms, and unsupported objects remain unchanged. |
| Text-only PDF | May not reach the target because there may be no eligible JPG data to reduce. |
| Vector-heavy PDF | May not reach the target because vector content is outside the JPG recompression scope. |
| Unsupported-image-heavy PDF | May not reach the target because unsupported image objects are preserved. |
A target can therefore be reachable for one PDF and impossible for another even when both contain images. JPG-heavy files have more opportunities for savings, but the final answer always depends on the actual document and the bounded profiles.
Review the downloaded file
A page-count check is a useful structural safeguard, but it does not certify every visual detail. After downloading the verified PDF, open it and review pages that contain photos, scanned text, fine graphics, forms, or links. Check that the layout remains suitable and that no important image detail was degraded by recompression.
You can also confirm the downloaded file’s size through its file properties on your device. It should be at or below the target that you entered. This provides an independent final check before submitting the document to a service with a strict upload limit.
For a more detailed review pass, use the checklist for reviewing a PDF after target-size compression. Retain the original until you have confirmed that the local result meets both the size requirement and your document-quality expectations.