About MoGuan
MoGuan (moguanpdf.com) is built by one independent developer. It is not a company, not a team, and it has no funding. You won't find phrases like "trusted by millions" or "built by ex-Big-Tech engineers" here — because none of that would be true, and I'm not going to invent it.
Who builds MoGuan
The reason I built this is plain. The popular online PDF tools (iLovePDF, Smallpdf, and the like) are genuinely good, but they all work the same way: you upload your file to their servers, they process it, and you download the result. For most files that's fine. But when the document is an unsigned contract, a résumé with an ID number, a bank statement, or a financial report, the act of sending the original to a stranger's server is uncomfortable on its own — no matter how nicely the privacy policy is worded. MoGuan's premise is simple: if it doesn't need to be uploaded, not a single byte gets uploaded.
Why client-side processing
The classic tools (merge, split, compress, rotate, delete pages, watermark, page numbers, crop, PDF↔image, sign, stamp, remove blank pages, Bates numbering, and more) are pure client-side with zero backend. The PDF you pick stays in your browser's memory from start to finish, processed with pdf-lib and pdf.js, with the result generated locally — no request ever sends your file anywhere. This isn't "encrypted upload," it's no upload at all. The honest distinction many privacy-marketing pages blur: MoGuan also has a few AI tools (summary, translation, Q&A, AI reflow) that send the text extracted from your PDF to an AI endpoint — what leaves your device is extracted text, never the original file, and every AI tool's UI says so. In one line: classic tools = zero upload; AI tools = text only, never the original.
Don't trust me — verify it
Trust shouldn't rest on "we care about your privacy" — anyone can write that. The advantage of client-side processing is that you can verify it on the spot. Run any classic tool (Merge or Compress PDF), press F12 to open DevTools and switch to the Network tab, clear the log, then use the tool and download. You'll see requests that load the page and scripts, but no upload request carrying your PDF's contents to a server. File in, file out — it never left your browser. That's the difference between client-side processing and a privacy policy: the first is an auditable fact, the second is a promise you're asked to believe.
Who it's for
MoGuan is a particularly good fit when the file itself is the sensitive information: legal/contracts (unsigned agreements, drafts with commercial terms), HR/recruiting (résumés with phone numbers, addresses, sometimes ID numbers), finance/personal (bank statements, tax paperwork, payslips), and anyone who'd simply rather not upload. MoGuan is bilingual (Chinese + English) and Chinese-first — many PDF tools treat Chinese as a machine-translated afterthought; MoGuan treated it as a first-class citizen from day one, including Chinese watermarks and Chinese OCR.
Contact
MoGuan is still actively being built; the tool count and details keep changing. If you hit a bug, want a specific tool, or have a question about what data ever leaves your device, email hello@moguanpdf.com. I maintain this alone, so replies may not be instant, but I read every message. As a solo developer, the most honest promise I can make isn't "we'll never misuse your data" — it's "for the classic tools I literally never receive your data, and you can confirm that yourself with DevTools."
FAQ
Is MoGuan really built by one person?
Yes. MoGuan is maintained by a single independent developer — no team, no company entity, no funding. I'd rather state that honestly than dress it up as "made by a team," because the whole point of this site is privacy and trust, and trust can't rest on fabricated credentials. What matters isn't how many people are behind it, but whether the classic tools actually upload your files — which you can verify yourself with DevTools.
Is "files never uploaded" just marketing?
For the classic tools (merge, compress, split, rotate, watermark, etc.) it's not marketing — it's a verifiable fact. On a tool page press F12, open the Network tab, clear the log, then use the tool and download. You'll see page/script requests but no request uploading your PDF's contents to a server.
What about the AI tools — is my file uploaded?
Your original PDF is never uploaded, but the text extracted from it is sent to an AI endpoint for processing, because the model needs to read the content. MoGuan states this on every AI tool's UI rather than blurring it under "everything runs in your browser." For documents that must never leave your device, use the classic tools only.
If nothing is uploaded, how can compression and merging happen in the browser?
Because modern browsers can run fairly complex processing themselves. MoGuan uses the open-source pdf-lib and pdf.js libraries to read and write PDFs directly in your browser's memory, with the result generated locally — no server involved, so your file stays on your machine the whole time.
Is it safe for sensitive documents like contracts, résumés, and financial reports?
MoGuan is designed exactly for this. For classic operations (merge, watermark, sign, compress, split, convert) the file never leaves your device — no third party (including me) can access its contents, and you can confirm zero uploads with DevTools. When using AI tools, remember they send extracted text (not the original); for highly sensitive content, stick to the classic tools.