Frequently Asked Questions

No. Every pdfmundo tool processes your files entirely inside your browser. The file you select stays on your device. It never travels to our servers, and we never have a copy of it. This applies to every tool in the catalog — Compress PDF, Merge PDF, OCR PDF, Sign PDF, all of them. Most other online PDF tools work the opposite way: they upload your file, process it on their servers, then send the result back. pdfmundo doesn't. You can verify this yourself in 30 seconds: open your browser's developer tools (right-click → Inspect, or press F12), switch to the Network tab, drop a file into any pdfmundo tool, and watch the Network tab during processing — you'll see no upload request to our servers.

Modern browsers can run compiled code at near-native speed through a W3C standard called WebAssembly (WASM). pdfmundo uses WebAssembly libraries — pdf-lib, pdf.js, Tesseract.wasm, and others — that load into your browser once, then process PDFs locally using your device's CPU and memory. The flow is straightforward: you select a file (browser file picker, on your device), the file loads into browser memory (your RAM, never our servers), WebAssembly code processes the file (your CPU), the result is offered for download (browser download dialog, on your device), and when you close the tab all file data is discarded from memory. The same operations that traditional cloud services run on rented servers now run inside your browser tab.

Yes. Because your files never leave your device, there's no file data to store, transfer, or share with third parties. The only personal data we process is what's strictly necessary for the service to work: anonymized server logs (IP, user-agent, URL, timestamp), retained 30 days for security; Pro tier email addresses for license delivery via Paddle; and any messages you send us at [email protected]. Full details in our Privacy Policy. To exercise your GDPR rights (access, rectification, erasure, portability, objection), email [email protected]. We respond within 30 days as required by GDPR Article 12.

No. We have no technical ability to see your file contents, names, or metadata. There's nothing to see — the files don't reach us. You can verify this by opening your browser's developer tools, switching to the Network tab, and processing a file. You'll see no upload requests. This is a structural property of the architecture, not a promise we ask you to trust. We literally cannot access what doesn't reach our infrastructure.

No. All processing happens in your browser's temporary memory. When you close the tab, that memory is released and the file data is gone. We don't write to your hard drive unless you explicitly click "Download." We don't use cookies to remember files between sessions.

For privacy specifically: yes, structurally. Server-based tools like iLovePDF and Smallpdf upload your files for processing. Even with TLS encryption in transit and stated retention policies, your file briefly exists on third-party infrastructure. pdfmundo's architecture removes that step entirely. For users handling legal, medical, financial, or otherwise sensitive documents, this is a meaningful difference. Server-based tools do have legitimate strengths — very large file handling, team collaboration, batch automation — that browser-only architectures don't match.

pdfmundo wins on architectural privacy and free-tier generosity — files never leave your device, free tier handles up to 50 MB with no watermarks, and the Pro yearly tier ($49) is meaningfully cheaper than iLovePDF ($48 but smaller free tier), Smallpdf ($108), or Adobe Acrobat ($180). iLovePDF and Smallpdf win on locale coverage today (25+ languages vs our 3, growing to 11) and native mobile apps. Adobe Acrobat wins on professional editing depth — deep text editing, PKI digital signatures certified under eIDAS, advanced form creation with XFA support. Stirling-PDF (open source MIT) wins for users willing to self-host via Docker and gets 50+ tools to our 30+. PDF24 wins on tool count alone. Each tool serves a different need; for users where architectural privacy is non-negotiable, pdfmundo is structurally different rather than just policy-different.

Standard web server logs: your IP address, browser user-agent, the URL you visited, and a timestamp. These are kept for 30 days for security and abuse prevention, then deleted. We don't log file processing activity, tool usage tied to individuals, or anything about the content you process. We don't use tracking cookies. We don't share data with advertisers.

Yes, and this is one of the strongest reasons pdfmundo exists. Lawyers handling privileged client documents, accountants processing tax records, healthcare workers redacting patient information, and journalists protecting sources all need to be certain their files aren't passing through someone else's infrastructure. Browser-only processing provides that certainty. The user remains responsible for compliance with their professional regulations: for HIPAA (US healthcare), browser-only processing avoids the Business Associate Agreement question entirely because no PHI reaches us as a covered entity, but you remain responsible for your own HIPAA controls. For attorney-client privilege, files never reaching third-party infrastructure preserves privilege in a way cloud-based tools cannot. For financial regulations (GDPR, GLBA, PCI-DSS, and similar frameworks), these have their own requirements you must meet independently. pdfmundo is a tool, not a compliance solution — we provide the architectural foundation; regulatory compliance remains your responsibility.

Browser-only processing means PHI (protected health information) in your PDFs never reaches us as a covered entity, so the typical HIPAA Business Associate Agreement question doesn't arise. That said, "HIPAA-compliant" is a property of your overall workflow, not of any single tool. You remain responsible for the security of the device processing the PDF, your network connection (TLS protects pdfmundo loading; your file processing is local), any export or sharing you do after processing, and workforce training, access controls, and audit logging on your end. If you handle large volumes of PHI under strict HIPAA oversight, consult your compliance officer before adopting any tool, including ours.

WebAssembly (WASM) is a low-level binary format that browsers can execute at speeds close to native applications. It was standardized by W3C in 2017 and is supported by every major browser. Before WebAssembly, complex file processing in a browser was slow and limited. With it, operations like PDF compression, image conversion, and OCR run efficiently on your local device — no server needed. pdfmundo's entire architecture depends on this technology. Without WebAssembly, browser-only PDF processing would not be performant enough to be useful.

Partially. The first time you visit, pdfmundo needs to download the tool's WebAssembly code from the server. After that, many tools continue to work even if you lose your internet connection mid-session. You won't be able to load a new tool without reconnecting, but the tool you're currently using will keep processing files locally. This makes pdfmundo unusually useful in conditions where most cloud tools fail: airplane Wi-Fi, rural connections, mobile data caps, regional internet outages, and locations where data sovereignty rules restrict cross-border file transfer.

Chrome 117 or newer, Edge 117 or newer, Safari 17.4 or newer, Firefox 137 or newer, Mobile Safari (iOS) 17.4 or newer, Mobile Chrome (Android) 117 or newer, and any Chromium-based browser (Brave, Opera, Vivaldi, Arc) of similar vintage. The version floor exists because pdfmundo uses recent WebAssembly features (SharedArrayBuffer, multi-threading support) that older browsers don't implement well. If a tool refuses to load, the most common cause is an outdated browser.

Because your laptop or phone is doing the work that a competitor's data center would normally do. A modern Mac or PC handles most operations as fast as a server, but for very large files (over 100 MB) or computationally heavy operations (compressing a 500-page scanned PDF with OCR), local processing can take longer than uploading to a server farm. This is the deliberate trade-off for keeping your file on your device. For most users with most files, the difference is unnoticeable. For edge cases (huge files, slow devices), server-based tools may genuinely be faster.

Yes. The interface is responsive and works on iOS and Android. The same browser-only architecture applies — your file stays on your phone. The practical constraint is memory: phones typically have less RAM than computers, so very large PDFs may fail or run slowly on mobile. For files under 50 MB, mobile works well for most tools.

Not currently. pdfmundo runs entirely in the mobile browser. We chose this over native apps for three reasons: native apps require Apple/Google revenue share (15-30%), raising prices for users; native apps require continuous platform maintenance that distracts from the core product; and the mobile browser experience already covers most use cases for a privacy-first tool. Native apps may come in 2027 if mobile-first emerging markets adoption justifies the investment. For now, "Add to Home Screen" from your mobile browser gets you an app-like icon and full-screen experience.

The free tier supports files up to 50 MB with 2 operations per day. Paid tiers (Day Pass, Credits, and Pro) support files up to 200 MB with no daily operation cap. There's no hard ceiling beyond 200 MB — the real limit is your device's available memory. Browsers typically allocate up to 2 GB to a single tab on modern computers, less on mobile. Files approaching the memory ceiling may slow down the browser or fail.

pdfmundo handles standard PDF files conforming to ISO 32000-1 (PDF 1.7) and ISO 32000-2 (PDF 2.0). This includes text, vector graphics, embedded fonts, images (JPEG, PNG, TIFF, JBIG2 in supported tools), AcroForm form fields, digital signature verification (creation of PKI-signed PDFs is not yet supported), bookmarks and outlines, metadata (Document Information Dictionary, XMP), optional content groups (layers), and encryption (40-bit RC4, 128-bit RC4, 128-bit and 256-bit AES). Specialized features with limited support include XFA forms (Adobe's older XML-based dynamic forms), embedded JavaScript actions, 3D content (U3D, PRC), and multimedia attachments.

Browser tabs have memory limits — typically 2 GB on desktop, 1 GB or less on mobile. A 300 MB PDF can require several gigabytes of working memory once it's parsed, decompressed, and held in browser memory during processing. For very large files, three alternatives work better than browser-only: desktop apps like Adobe Acrobat or Foxit (which can write temporary files to disk), server-based tools (which have effectively unlimited memory), or splitting the file first with Split PDF, then processing pieces individually with pdfmundo. This is an honest limit of the browser-only approach, not a bug.

Yes, for tools where it makes sense — Merge PDF, JPG to PDF, and similar tools accept multiple files in a single operation. Each file is still processed locally; batching is a UX convenience, not a server-side operation. Free tier users have a per-day operation cap (2 conversions per 24 hours); paid tiers have no daily cap.

If your PDF is password-protected, remove the password in your own PDF software before uploading it to pdfmundo — most PDF readers, and the app that created the file, can do this once you know the password. If you only want to add or change a password, use Protect PDF, which supports 128-bit and 256-bit AES encryption.

The free tier gives you access to all 30+ tools, up to 2 operations per day, with files up to 50 MB. No account needed. No ads. No watermarks added to your files. For most casual users — a few PDF tasks a week — the free tier is genuinely all you need. Paid tiers exist for people who process files frequently, need larger file sizes, or want to support the project.

Four tiers cover different usage patterns: $1.99 day pass, $4.99 credits, $5.99/mo Pro, or $49/annual Pro annual. Day Pass is one batch of work, no commitment. Credits are 50 operations that never expire — good for occasional heavier use over weeks or months. Pro Monthly is regular professional use. Pro Yearly saves about 32% versus monthly billing. All paid tiers include files up to 200 MB and unlimited operations within their structure.

Payment is handled by Paddle, an established UK-based payment processor. Paddle acts as the Merchant of Record, meaning they handle the transaction, the VAT calculation for your country, and the invoice. Your credit card details are entered into Paddle's checkout, not into pdfmundo — we never see your card number. Paddle supports a wide range of payment methods globally: major credit cards (Visa, Mastercard, American Express), PayPal, Apple Pay and Google Pay, plus regional methods like UPI and RuPay (India), Pix (Brazil), Multibanco and MB WAY (Portugal), iDEAL (Netherlands), Bancontact (Belgium), SOFORT and Giropay (Germany), Alipay and WeChat Pay (China).

Yes. EU consumers have a 14-day right of withdrawal for digital services under EU consumer law. For other regions, refund requests are handled by Paddle on a case-by-case basis. Email us at [email protected] or contact Paddle directly. Refunds for genuine product issues — a tool that didn't work for you — are generally granted without friction.

No, not for the free tier or Day Pass. Pro and Credits use an email-based license: you enter your email at checkout, Paddle sends you a license key, you paste it into pdfmundo to activate Pro features. There's no traditional account with a password to remember. This is a deliberate choice — fewer accounts means less data we hold about you.

Yes, for teams of 5 or more. Email [email protected] to discuss. We support most arrangements: per-seat pricing, single-license-multi-user with reasonable use, and enterprise invoicing for larger organizations.

Honest answer: no PDF-to-Word converter produces perfect results, ours included. PDF and Word are fundamentally different formats — Word stores editable text flow, PDF stores fixed page positions. Our converter handles most cases well: typed text, basic tables, simple layouts. Complex layouts with multi-column text, irregular tables, or graphic-heavy designs may need cleanup after conversion. For documents where perfect formatting matters — legal contracts, official forms — recreate them in Word from scratch rather than relying on any automatic converter (ours, Adobe's, or anyone else's).

Yes. OCR PDF uses Tesseract.wasm and supports over 100 languages. Latin script coverage includes Spanish, Portuguese, French, German, Italian, Polish, Romanian, Dutch, Czech, Hungarian, and Turkish. Cyrillic coverage includes Russian, Ukrainian, Bulgarian, and Serbian. CJK coverage includes Chinese (Simplified and Traditional), Japanese, and Korean. Arabic script coverage includes Arabic, Persian, and Urdu. Indic coverage includes Hindi, Bengali, Tamil, Telugu, Gujarati, and Marathi. Other supported languages include Greek, Hebrew, Thai, Vietnamese, Indonesian, and Malay. Mixed-language documents are supported. OCR accuracy depends on scan quality — clean 300 DPI scans of printed text typically reach 95%+ accuracy; poor scans of handwriting or stylized fonts are much harder.

Different tools for different needs. Adobe Acrobat is the most powerful PDF editor available, with deep text editing in PDFs, advanced form creation including AcroForm and XFA support, PKI digital signatures certified under eIDAS, redaction with verification, OCR with format preservation, and batch processing automation. pdfmundo handles common operations with browser-only privacy at a fraction of the cost — Pro yearly ($49) is roughly a quarter of Acrobat Pro's annual subscription. The trade-offs are real: for professional editing of complex documents — multi-column legal contracts, dynamic XFA forms, eIDAS qualified signatures — Acrobat remains the right tool. For everyday PDF tasks where files never leaving your device matters, pdfmundo covers what most people need.

Our Sign PDF tool adds a visible signature image to your document — useful for routine business documents, internal approvals, and many contracts. It produces what eIDAS calls a "simple electronic signature." It does NOT create a PKI-based digital signature certified by a qualified trust service provider (QTSP) under eIDAS Regulation 910/2014, nor a qualified electronic signature (QES) with the legal equivalence to a handwritten signature in the EU, nor a signature satisfying the Federal ESIGN Act's stricter requirements for specific document categories in the US. For legally binding signatures requiring these levels of verification — EU regulated industries, specific real estate transactions, certain financial instruments — use a dedicated service such as DocuSign, Adobe Sign, or a qualified trust service provider in your country.

Not currently. The processing libraries we use — pdf-lib, pdf.js, Tesseract.wasm — are open source; you can verify their source code on GitHub. The pdfmundo application layer that combines them is closed source. If open source is a hard requirement for you, Stirling-PDF is the leading self-hostable alternative. It's a different architecture — server-based, self-hosted via Docker — but the source code is fully auditable.

Both protect privacy, by different mechanisms. Stirling-PDF is server-based, self-hosted via Docker, MIT-licensed open source, and free if you have hosting. It offers 50+ tools and requires you to maintain the server. pdfmundo is browser-only WebAssembly, zero setup, and runs anywhere a modern browser does. It offers 30+ tools, requires no maintenance from you, and works on mobile out of the box. Stirling-PDF wins if you have technical skills and want full control. pdfmundo wins as the zero-setup option that delivers the same privacy property — files never leaving your device — through a different mechanism.

For tax document handling specifically, three properties matter most: the tool never uploads your financial documents anywhere, it can compress PDFs to meet government portal size limits, and it preserves text searchability. pdfmundo's Compress PDF and Merge PDF cover all three. For specific government portals — US e-file, UK HMRC, EU MyTax, country-specific tax authorities — check their stated size limits and use Compress PDF with the small file preset.

Most government forms cap PDF uploads at 2-5 MB. Compress PDF handles this for nearly all typical documents in five steps: open Compress PDF, drop your file into the upload zone, choose compression level (Small file, Recommended, or Less compression), wait 5-30 seconds for local processing, then download. If the result is still too large, two follow-ups work: for scanned PDFs, run OCR PDF first to convert images to text then compress (often reduces 50-80%); for mixed-content PDFs, split into pages, compress separately, then re-merge.

For India-specific government workflows — Aadhaar uploads, ITR filings, college admissions, passport applications — pdfmundo handles the common file size limits (typically 100KB-5MB per document) and supports Hindi OCR for scanned regional-language documents. All processing happens on your device, so sensitive identity documents like Aadhaar PDF copies never reach foreign servers. Hindi locale support is on our 2026 roadmap; in the meantime, English instructions cover the Indian government workflow vocabulary directly.

For Brazilian workflows — DARF tax forms, e-CAC submissions, MEI documents, INSS receipts — pdfmundo handles Portuguese-language documents natively, supports OCR for scanned Receita Federal correspondence, and compresses to fit common government portal limits. Paddle accepts Pix for payment in BRL. Brazilian Portuguese readers should know the current PT locale is European Portuguese; a Brazilian variant is on our 2026-2027 roadmap.

For Latin American workflows — Mexican CFDI invoices, SAT declarations, Argentine AFIP submissions, Chilean SII, Colombian DIAN — pdfmundo handles Spanish-language documents natively, supports OCR for scanned correspondence, and compresses to fit common government portal limits. Paddle accepts local credit cards in Mexican pesos, Argentine pesos, Colombian pesos, and other regional currencies. All processing happens on your device, so identity and financial documents never reach foreign servers.

For Spanish workflows — Modelo 100, IRPF declarations, IVA filings, Seguridad Social, municipal registries, sede electrónica DGT — pdfmundo handles Castilian Spanish documents natively, supports OCR for scanned correspondence, and compresses to fit standard sede electrónica limits. Paddle accepts Spanish cards and Bizum for payments in euros with proper Spanish IVA invoicing.

For Portuguese workflows — IRS declarations, Modelo 3 attachments, Segurança Social, certidões prediais, e-Fatura submissions — pdfmundo handles European Portuguese documents natively, supports OCR for scanned correspondence, and compresses to fit Portal das Finanças limits. Paddle accepts Multibanco and MB WAY for payments in euros with proper Portuguese invoicing.

Yes. Three tools cover the common job-application workflow: Compress PDF handles the 2 MB cap most job portals enforce on resume uploads without losing readability; PDF to Word converts to .docx for ATS (applicant tracking system) compatibility when employers require Word format; Merge PDF combines resume, cover letter, and portfolio into a single navigable file. Browser-only processing matters here too — your CV stays on your device rather than passing through third-party servers during conversion.