Why Isn't My PDF Tool Working? A Troubleshooting Guide
Because browser-based PDF tools like PDFcraft run entirely on your device (see our full explainer if you want the details), when something goes wrong, it's happening in your browser rather than on a distant server — which means most problems are diagnosable and fixable on your end in under a minute. Here's what each symptom usually means, based on how these tools are actually built.
"Nothing happens when I click the button"
Check for a progress indicator first
Some tools (like Compress PDF) show a brief 'Processing...' state with a spinner. For small files this can pass in well under a second — if you blinked, it may have already finished. Scroll down slightly to check for a result.
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
These tools require JavaScript to run at all (there's no server fallback). If you're using a strict content blocker or privacy extension, it may be blocking page scripts entirely. Try temporarily disabling extensions for this site.
"I got a generic error message"
Every tool wraps its processing in error handling that shows a simple alert if anything goes wrong internally — by design, this catches the failure gracefully instead of leaving the page broken, but it doesn't always say why it failed. Here are the actual, verified causes:
The PDF is password-protected
This is the single most common cause. Tools like Merge PDF cannot open an encrypted PDF without the password — the underlying library refuses to load it at all. If your file needs a password to open normally, use Unlock PDF first, then try your original tool again.
The file isn't actually a valid PDF
If a file has a .pdf extension but is corrupted, incomplete, or is actually a different file type renamed to .pdf, the PDF-parsing step will fail immediately with the same generic error.
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"
The file picker is set to suggest PDF files by default, which is a hint for the operating system's file browser — not a hard restriction. If you're dragging and dropping a non-PDF file, or selected 'All Files' in the picker, the tool will still try to process it and fail at the parsing step above rather than rejecting it upfront. Image tools (like JPG to PDF) specifically check that selected files are actual images and will tell you directly if none qualify.
"The page froze or my browser crashed on a large file"
There's no artificial file size limit — your device's memory is the real ceiling
PDFcraft doesn't cap file size in code. The tradeoff of processing on-device is that a very large file (hundreds of MB, or PDFs with hundreds of high-resolution pages) can use up available browser memory, especially on phones, which have less RAM available to a single browser tab than a laptop or desktop.
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
If a large file consistently freezes on mobile, the same file will very likely process fine on a computer, which typically has significantly more memory available per browser tab.
Split the PDF into smaller pieces first
For genuinely huge documents, processing 50 pages at a time instead of 500 reduces the memory needed at once. This does mean a chicken-and-egg problem if Split itself struggles with the same huge file — in that case, a desktop browser is the more reliable path.
"My download didn't start"
Check your browser's download prompt or blocked-popup indicator
The download is triggered automatically by the page — some browsers show a small notification asking you to confirm, which can be easy to miss.
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
- Is the PDF password-protected? → Unlock it first, then retry your original tool.
- Is the file actually a PDF (not renamed from another format)? → Open it in another PDF viewer to confirm.
- Is the file very large (100MB+) or very long (100+ pages)? → Try on a desktop browser, or split it first.
- Do you have content-blocking extensions enabled? → Temporarily disable them for this site.
- Did you check your Downloads folder? → The file may have saved without an obvious confirmation.
💡 Pro tip
If a specific file consistently fails on every attempt, the fastest diagnostic is trying a different, smaller PDF on the same tool. If the small file works fine, the issue is almost always specific to that file (password, corruption, or size) rather than the tool itself.
Related reading
Frequently asked questions
Why doesn't the error message tell me exactly what went wrong?
The current error handling shows a simple, consistent message rather than exposing internal technical details. It's a real limitation — this guide exists specifically to fill in what the generic message doesn't say.
Is there a file size limit on PDFcraft?
No artificial one. The practical limit is your device's available memory, which varies by device — see the large-file section above for what to do if you hit it.
Will my file be lost if a tool fails partway through?
Nothing is uploaded or saved anywhere in the first place, so there's nothing to recover — your original file on your device is untouched. Just try again.
Does this happen because of a bug, or is it expected behavior?
Most of what's described here is expected behavior given how the tools are built (see how it works), not a malfunction — though if you hit something that isn't covered here, that's useful to know about.
Try your file again — most issues resolve on retry
Free, instant, private. No sign up required.
Try it free →