I recently launched PixoPDF, a free browser-based PDF toolkit focused on local document processing.
While building it, I kept thinking about one thing: people upload resumes, contracts, financial documents, forms, and other sensitive files to online PDF tools every day. But how often do we actually check where those files are processed?
With PixoPDF, supported document workflows are processed directly in the browser. There's no mandatory signup and no watermark.
I'm curious does local browser processing make you trust a PDF tool more? Or do speed, conversion quality, and ease of use matter more when choosing one?
local browser processing for 34 tools is a real engineering lift, not just a marketing line, merge/split is easy client side but OCR and heavy compression usually push people to a server. did you have to cut any features because they weren't practical to run fully in-browser, or does everything on the list genuinely run client side including the heavier stuff?
@omri_ben_shoham1 Yes, everything on the list genuinely runs 100% client-side inside the browser tab, but we definitely had to make architectural trade-offs to keep it fast and prevent browser tabs from crashing.
the privacy pitch is solid but the one tool on that list I'd want to stress test before trusting it is redaction. the classic failure mode with PDF redaction tools isn't the browser vs server question, it's tools that just draw a black box over the text while the actual characters (or an OCR text layer) are still sitting underneath, so anyone can select-all or copy-paste the "redacted" content right out. does PixoPDF's redact tool actually strip the underlying content, or is it a visual overlay
@galdayan That's the #1 vulnerability with PDF redaction tools, but PixoPDF does not use visual overlays. It uses a fully-destructive client-side flattening process: the page is rendered onto a high-definition canvas (150 DPI) using PDF.js, black boxes are painted directly onto the canvas pixels with 5px safety padding, and then pdf-lib completely deletes the original page node from the PDF’s catalog structure (doc.removePage()) and replaces it with a brand-new blank page containing only the flattened canvas image. Because the original page object is destroyed, 100% of the underlying font files, text streams, and vector paths are permanently erased from the PDF binary, leaving zero selectable text or OCR metadata behind the black boxes.
@pganeshkrishnareddy that's a genuinely solid answer, most tools don't bother explaining the mechanism that clearly. one follow-up - what about metadata outside the page content itself, things like document properties, XMP metadata, or embedded attachments/annotations elsewhere in the file. does the redact flow scrub those too, or is it scoped strictly to the visible page content?
@galdayan That's a great question and honestly, it's something we paid a lot of attention to while building PixoPDF.
Right now, the Redact PDF tool is designed to permanently remove the visible content on the page by rebuilding the redacted page, instead of simply placing black boxes over the original text.
Document-level metadata (like PDF properties or XMP) isn't automatically removed as part of the redaction workflow today. That's why we also have a separate Remove PDF Metadata tool for users who want to clean document properties before sharing a file.
I'm also working on a Secure Redaction mode that will combine page redaction, metadata cleanup, annotation removal, and other sanitization steps into a single workflow. Thanks for bringing this up—it's exactly the kind of feedback that helps make the product better. 🚀
@pganeshkrishnareddy that clears it up, and the separate metadata tool makes sense as a distinct step rather than bundling it silently into redaction. the combined Secure Redaction mode sounds like the right end state - most people assume redact = fully sanitized and get burned by exactly this gap. will keep an eye out for it
Compressed a 40-page report and was honestly surprised it stayed readable, not the usual mushy scanned look. Love that nothing leaves my browser.
@berkaybykklycp Thank you Berkay! We put a lot of work into the image downscaling algorithms to ensure text remains crisp and highly legible even after reducing the file weight. Appreciate the feedback!
merged a few contracts right in chrome without uploading anything, which is exactly what i needed. the local processing claim seems legit since it worked offline too.
@mesutyarar10494 Thanks Mesut! Working completely offline is the ultimate test of our client-side architecture. Glad it came in handy for your contracts with absolute privacy!
Merged a few contracts with it on a whim and it was surprisingly fast, finished the whole batch without anything leaving my laptop which is honestly the main thing I want from a pdf tool.
@cemileengiy4nr Merged a few contracts with it on a whim and it was surprisingly fast, finished the whole batch without anything leaving my laptop which is honestly the main thing I want from a pdf tool.