How to reduce pdf file size with grayscale conversion
- Step 1Check whether grayscale is even the right lever — If your PDF is mostly colour photos or scans, grayscale can shrink it. If it's mostly text, stop here and use lossless compress instead — grayscale will likely enlarge a text PDF.
- Step 2Open the grayscale converter — Load your file into PDF Grayscale. Conversion is automatic on drop; there are no settings.
- Step 3Read the before/after size tiles — The result panel shows Input size and Output size side by side. This is your instant verdict — if Output is bigger, grayscale didn't help and you should discard it and use a compressor.
- Step 4Chain into a compressor if you need a target size — Grayscale alone rarely hits a hard number like "under 1 MB". Take the grey output and run it through aggressive compress, which searches quality and resolution to land under a target.
- Step 5Compare against compressing the original directly — Often the aggressive compressor on the colour original gets you smaller than grayscale-then-compress, because it controls quality and resolution. Try both and keep the smaller.
- Step 6Download and verify it opens — Download the
*.grayscale.pdf, open it, and confirm the pages render. Remember the text is now an image, so check that any small text is still legible at the size you'll use it.
When grayscale shrinks the file — and when it grows it
The deciding factor is what's on the page. Colour imagery shrinks; crisp text grows. These are typical directions, not guarantees.
| PDF content | Size after grayscale | Better tool for size |
|---|---|---|
| Colour photos / scans | Usually smaller (colour channels dropped + JPEG re-encode) | Aggressive compress for a target size |
| Colour slide deck export | Often smaller, but compressor wins on a hard target | Aggressive compress |
| Mostly text (report, contract) | Usually larger (text becomes a JPEG) | Lossless compress |
| Bloated metadata only | Larger (you rasterised the whole thing for no reason) | Metadata scrubber |
Why grayscale is a blunt size lever
What grayscale controls vs what a real compressor controls. The gap is why a compressor usually wins on size.
| Knob | Grayscale tool | Aggressive compressor |
|---|---|---|
| Drops colour channels | Yes | Yes (when you choose grey) |
| Adjustable JPEG quality | No — fixed at 0.92 | Yes — searched per page |
| Adjustable resolution / DPI | No — fixed at 2× render | Yes — stepped down if needed |
| Targets a specific size (e.g. 1 MB) | No | Yes |
Tier limits for the in-browser converter
Real PDF-family limits from the app configuration. The size limit applies to the input file you drop in.
| Tier | Max input size | Max pages |
|---|---|---|
| Free | 2 MB | 50 |
| Pro | 50 MB | 500 |
| Pro + Media | 500 MB | 2,000 |
Cookbook
Measured-style results showing both directions — grayscale helping and grayscale hurting. Your numbers depend on content.
Photo-heavy brochure shrinks
A colour product brochure that is almost all photography. The colour channels are the bulk of the bytes, so grayscale helps.
Input: brochure.pdf colour, 8 pages, 6.4 MB (Pro) Output: brochure.grayscale.pdf grey, 8 pages, ~3.0 MB Then aggressive compress to a target if you need smaller: → ~1.0 MB under target.
Text report grows (the trap)
A text-only quarterly report. Grayscale rasterises crisp text into JPEGs and the file balloons. This is the classic mistake.
Input: report.pdf colour text, 20 pages, 480 KB Output: report.grayscale.pdf grey, 20 pages, ~1.6 MB ✗ bigger! Correct tool: lossless compress (keeps text, shrinks structure) → ~360 KB, text still selectable.
Scan: grayscale vs compress-direct
A colour scan. Both grayscale and the aggressive compressor help — but compressing the original directly often wins, because it controls quality and resolution.
Input: scan.pdf colour, 10 pages, 22 MB (Pro) Grayscale only: ~9 MB Aggressive compress (orig): ~1.8 MB ← smaller Keep the aggressive-compress result.
Reading the verdict from the tiles
The result panel tells you instantly whether grayscale helped — no need to check the file on disk first.
Result tiles after conversion: Input size: 6.4 MB Output size: 3.0 MB ← helped, keep it If Output > Input, discard and use a compressor instead.
Two-step pipeline for image-heavy files
When grayscale does help, follow it with a compressor for the best of both.
Step 1: grayscale → brochure.grayscale.pdf (3.0 MB)
Step 2: aggressive compress, target 1024 KB
→ 0.95 MB, targetMet: trueEdge cases and what actually happens
Text PDF gets larger after grayscale
Expected (wrong tool)Crisp vector text re-encoded as a JPEG is larger than the original. If your PDF is mostly text, grayscale is the wrong tool for size — use lossless compress, which shrinks the file structure while keeping text selectable.
Grayscale can't hit a hard size target
Use compressorThere is no quality or resolution control here, so grayscale can't aim for "under 1 MB". Use aggressive compress, which binary-searches quality (and drops resolution if needed) to land under a number you set.
Selectable text is lost
By designEvery page becomes a grayscale image, so text selection and search are gone. That's inherent to how this tool reduces colour-image bytes. If you need text preserved, the lossless compressor is the size tool that keeps it.
Compressing the original beats grayscale-then-compress
Try bothOn a colour scan, running the aggressive compressor on the original often produces a smaller file than greying it first, because the compressor controls quality and resolution too. Try both paths and keep the smaller result.
Input exceeds the tier size limit
BlockedFree tier blocks files over 2 MB or 50 pages with an upgrade prompt. A large colour PDF you're trying to shrink may itself be over the limit — Pro raises it to 50 MB / 500 pages, or split the file first.
Output looks softer at high zoom
ExpectedPages are JPEG-encoded at fixed quality 0.92. That's high quality but lossy, so fine detail softens slightly. At normal viewing or print size it's invisible; only deep zoom reveals it.
A line-art / vector diagram PDF
Likely growsVector line art is extremely compact and sharp. Rasterising it to a grey JPEG usually enlarges the file and adds softness. Keep it as vector and compress losslessly instead.
Bloat is actually metadata or fonts
Wrong targetIf the file is big because of embedded metadata or duplicate resources rather than imagery, grayscale won't help and adds cost. Use the metadata scrubber or lossless compress to target the real bloat.
Very large or long PDF is slow
Slow but completesBrowser rendering of many pages takes time and memory. It finishes, but splitting a long document first makes each pass faster and lighter.
Frequently asked questions
Does converting to grayscale really make a PDF smaller?
Only sometimes. For colour-photo or scan PDFs, dropping the colour channels and re-encoding as JPEG usually shrinks the file. For text-heavy PDFs it usually grows the file, because crisp vector text becomes a (larger, softer) JPEG image. Check the Input vs Output size tiles — they tell you instantly whether it helped.
How much smaller can I expect?
On photo-dominated PDFs, roughly 30–60% before any further compression — but it varies a lot with content. On text PDFs, expect it to get bigger. There's no quality control to push it further, so for predictable reductions chain into a compressor.
Can I combine grayscale and compression?
Yes. Convert to grayscale first, then run the grey output through aggressive compress to hit a target size. But also try compressing the colour original directly — on scans that often wins, because the compressor controls quality and resolution too.
Why did my text PDF get bigger?
Because grayscale rasterises every page into a JPEG. A page of crisp text is tiny as vector data but bulky as a JPEG, so the file grows. Text PDFs should use lossless compress, which keeps text selectable and shrinks the structure instead.
Will text quality suffer?
Visually, slightly — text is re-encoded as a JPEG at quality 0.92, so it softens marginally and is no longer selectable. At normal sizes it reads fine; very small text may look fuzzy. If crisp, selectable text matters, don't use grayscale for size.
Is there a quality or DPI setting to control the size?
No. This tool has no options — quality is fixed at 0.92 and the render is fixed at 2× scale. If you need to tune quality, resolution, or a target size, that's exactly what the aggressive compressor is for.
What's the single best way to make a colour PDF small?
For image-heavy files, the aggressive compressor with a target size usually beats grayscale, because it controls quality and resolution. For text-heavy files, the lossless compressor is best — it keeps text selectable. Grayscale is the right pick only when you also want a mono document.
Does it strip metadata too?
Re-rendering the pages drops the old document structure and most metadata as a side effect. But if removing metadata is your only goal, the metadata scrubber does it losslessly without rasterising anything.
Is my file uploaded?
No — everything runs in your browser and the result panel confirms 0 bytes uploaded. Even large source PDFs you're trying to shrink stay entirely on your device.
What's the file-size limit?
Free tier handles inputs up to 2 MB and 50 pages; Pro up to 50 MB and 500 pages. Ironically, a colour PDF big enough that you want to shrink it may exceed the free limit — split it first or upgrade.
Will the output open everywhere?
Yes. The result is a standard PDF with one grayscale image per page, which every reader, browser, and upload portal handles. It's about as universally compatible as a PDF gets.
Should I run grayscale twice to shrink further?
No — re-running it on an already-grey, already-JPEG'd file just degrades quality for little or no size gain. Convert once, check the tiles, and if you need it smaller, switch to a compressor on the original rather than re-processing the output.
Privacy first
All PDF processing runs locally in your browser using PDF-lib and pdf.js. No file is ever uploaded — only metadata counters are saved for signed-in dashboard stats.