Prompt
My merged PDF pages are coming out blank, what's going wrong?
Latest observation
Nov 21, 2026
OpenAI APIWeb search: off
A merged PDF coming out blank usually means one of a few common things is happening during the merge process:
Common causes
-
You’re merging image-only PDFs incorrectly
- If the pages are scans or images, some tools can create blank-looking pages if they don’t preserve the image layer properly.
-
The PDF is using unsupported content
- Things like transparency, annotations, forms, layers, or unusual fonts can sometimes get dropped or rendered as blank during merge.
-
Page rotation / crop box issues
- The content may still be there, but it’s outside the visible page area because of incorrect page boxes.
-
The source files are already broken
- Open the original PDFs separately. If they’re blank there too, the issue isn’t the merge step.
-
Wrong library or settings
- Some PDF libraries require you to render pages to new pages rather than just copy page objects.
- Others need explicit handling for images, backgrounds, or page dimensions.
-
Encryption / permission issues
- Some protected PDFs may merge but lose content if they’re not fully decrypted first.
Quick checks
- Open each source PDF individually.
- Try merging with a different tool to compare.
- Inspect whether the output has page count but no visible content.
- Check whether the pages are actually blank, or just white-on-white / off-canvas.
If you're coding it
The fix depends on the library:
- PyPDF2 / pypdf: usually fine for simple PDFs, but some complex PDFs can render badly in some viewers.
- ReportLab + image insertion: if you’re converting scans, make sure the images are drawn onto each page.
- Ghostscript / qpdf / pdftk: often better for direct PDF processing if your current tool is stripping content.
Best next step
Tell me:
- what language/library you’re using,
- a small code snippet,
- and whether the source PDFs are scans or text-based,
and I can pinpoint the likely cause.