Why Isn't My PDF Tool Working? A Troubleshooting Guide
Start with the actual error and a non-sensitive sample when a tool fails. The cause may be the document, browser resources, a blocked runtime download, or a product defect. Local document processing does not mean every failure is local or user-fixable.
Match the error to a useful next step
These examples follow the current validation paths. A refusal is not always evidence that your PDF is damaged: some valid document features are deliberately unsupported.
| What you see | What it means | Next step |
|---|---|---|
| PDF could not be read | The parser could not accept a complete document with at least one page. | Open the original in a PDF viewer. Re-download an incomplete file; renaming its extension does not repair it. |
| Unsupported AcroForm or navigation | The page-copy workflow cannot safely rebuild that document structure. | Use a PDF application that supports the form or navigation. Do not discard an original form merely to bypass the check. |
| Invalid or out-of-bounds range | Split needs ascending page ranges within the actual page count. | For a three-page PDF use 1-2,3. Avoid 3-1, page 4 or a trailing comma. |
| Could not load the PDF security engine | The qpdf runtime was unavailable before password processing. | Check connection and blocked-resource messages, then retry. A different password cannot repair a missing runtime. |
| QPDF status failure | The password may be wrong, or the document may be damaged or unsupported. | Confirm the known password in a trusted viewer. GetPDFCraft cannot recover an unknown password. |
| Rendering limit exceeded | A page or the total encoded images exceed the renderer's guardrails. | Split into smaller groups if possible. A single oversized page needs a desktop application or a smaller page from the source. |
"Nothing happens when I click the button"
Check for a progress indicator first
Look for the tool’s current progress/status and result area. Compress starts after file selection; it has no separate Compress button.
Large files take time proportional to your device
Since processing happens on your device rather than a server, a large or complex PDF on an older phone can take noticeably longer than the same file on a laptop. Give it a few extra seconds before assuming it's stuck.
Check if JavaScript is disabled or blocked
The tools require JavaScript. Inspect whether a required page script or runtime is blocked; do not disable security settings indiscriminately.
"I got a generic error message"
Error reporting varies by tool: some show inline messages, and some still use alerts. Protect/Unlock distinguish runtime-loading failures from qpdf status errors, but a status failure can still mean a wrong password, damaged PDF, or unsupported input.
The PDF is password-protected
Many page tools reject encrypted input. Unlock an authorized copy with its correct password before retrying. GetPDFCraft does not crack unknown passwords.
The file isn't actually a valid PDF
A .pdf extension does not prove valid PDF bytes. Several tools validate the header or parsing result; damaged or incomplete files can fail. Obtain a valid copy if needed.
The PDF uses an unusual or non-standard internal structure
Some PDFs — particularly very old ones, or ones produced by uncommon software — use structures that trip up parsing libraries. This is rare but not impossible. Try opening the file in a different PDF viewer first to confirm it isn't corrupted.
"The tool won't accept my file"
File-picker accept settings are hints, not full validation. JPG to PDF validates JPEG/JPG and PNG bytes and rejects unsupported formats. PDF validation differs by tool; renamed or damaged input may fail before or during parsing.
"The page froze or my browser crashed on a large file"
Check rendering limits as well as available memory
PDF to Image and Grayscale stop above 16 million pixels per page, 16,384 pixels per side or 128 MiB of encoded page images. These guards do not guarantee enough memory: a device can fail below them. Other PDF operations are also limited by document complexity and available resources.
Close other tabs before processing a large file
Each open tab competes for the same pool of memory. Closing unused tabs — especially other media-heavy ones — frees up room for the PDF tool to work.
Try on a desktop or laptop instead of a phone
A different device or browser may have more usable resources, but success is not guaranteed. Test the same non-sensitive file to narrow the cause.
Split the PDF into smaller pieces first
If Split can load the file, explicit page ranges can divide it into parts. Split itself still needs to load the source and may fail on the same input.
"My download didn't start"
Check your browser's download prompt or blocked-popup indicator
Click the result’s Download control and check the browser’s download prompts. PDF-to-image Download All triggers separate downloads and may need browser permission.
Check your Downloads folder even if nothing seemed to happen
Some browser configurations save files silently without a visible prompt.
Try a different browser if it persists
This flow relies on standard browser download behavior. It's rare, but browser extensions or unusual privacy settings can occasionally interfere with it.
Quick diagnostic checklist
- Does the input open in a compatible viewer?
- If encrypted, do you have the correct password and authorization to modify it?
- Can the browser load the tool’s required worker or WASM runtime?
- Does a smaller, non-sensitive file work with the same tool?
- Check the browser download list and chosen save location.
💡 Pro tip
Testing a smaller file can help narrow the cause, but does not prove that the product has no bug. Report the error through Contact without sending sensitive documents or passwords.
Related reading
Frequently asked questions
Why doesn't the error message tell me exactly what went wrong?
A processing error can have several causes. For Protect/Unlock, a qpdf status failure alone cannot reliably distinguish a wrong password from a damaged or unsupported PDF.
Is there a file size limit on GetPDFCraft?
Practical limits depend on browser capabilities, available memory, and document complexity. A large or complex file may fail; keep your original and check the downloaded result.
Will my file be lost if a tool fails partway through?
The selected source is not overwritten by processing. Preserve it when saving downloads; cleanup is not a secure-erasure guarantee.
Does this happen because of a bug, or is it expected behavior?
Either is possible. File validity, resources, runtime access, and application defects can cause failures. Keep the actual error when asking for help.