Primary sources checked 8 August 2026

FileGizmo vs browser PDF tools

Privacy is no longer a rare feature. The useful question is what each product does locally, what it can edit, and what happens to the words underneath a visual replacement.

Reviewed

What the current sources actually support

The table distinguishes a vendor claim from an inference. “Not documented” means the checked source did not answer that narrow question.

QuestionFileGizmoHonestPDFQuicklyPDFiHatePDFAservusClientPDF
Published catalog124 live file tools across PDF, image, CSV, text, and developer workHomepage linked a broad PDF catalog, including edit, fill, OCR, conversion, and security toolsMaker page lists merge, split, compress, conversion, and extraction; form filling and signing were marked coming soon35+ tools advertised, including editor, conversion, OCR, comparison, and Bates numbering23 named PDF, converter, and utility tools on the homepage28 tools advertised, including sanitize, redact, OCR, sign, and core page operations
Processing pathOrdinary file tools run locally under a same-origin connection policyAll tools described as in-browser and offline after first loadMixed: many operations local; advanced conversions use server-side components and one-hour deletionMixed: browser mode is advertised; the homepage also documents server processing with immediate deletionMixed: local when possible; heavy tasks use encrypted servers with one-hour deletionAll processing described as local, with offline app support
Edit existing PDF textYes, for selectable textAn Edit PDF tool is linked, but existing-text behavior is not documented on the checked overviewEditing is named generally, but existing-text behavior is not documented in the detailed maker descriptionYes. Editly advertises editing text and contentThe homepage says edit, but its published tool list does not document an existing-text editorNot documented on the checked 28-tool overview
Remove the words under a replacementOptional. Rasterize corrected pages to remove the old text, with a clear loss of search and selectionNot documented for text replacement in the checked sourceNot documented in the checked sourceUnderlying content-stream behavior is not documented on the checked editor overviewNot documented in the checked sourceNot documented in the checked source
A strength worth creditingOne catalog for five file categories, measurable privacy proof, local autosave, and explicit export tradeoffsStrong local-only position, offline use, privacy scanner, metadata removal, and a substantial PDF catalogLocal handling for common operations plus server engines for higher-fidelity office conversionThe broadest advertised specialist set here, with direct text editing and documented server deletionA practical mix of browser tools, repair, office conversion, and clear disclosure that heavy tasks use serversFocused local PDF studio with sanitize, permanent redaction, offline use, and no account

FileGizmo’s editor boundary

FileGizmo does not rewrite text operators inside the PDF content stream. When you replace selectable text, the editor samples the page background, covers the old visual area, and draws new text over it. That approach works across more documents than pretending every embedded font and positioned glyph can be safely rewritten. It also leaves the original words inside the file by default.

The editor warns about that consequence when a replacement is made. If the old words must be gone, the flatten option exports corrected pages as images. This removes the underlying wording, but it also removes search, selection, and accessible text on those pages. For a paragraph that must reflow, edit the source document and export a new PDF. For regulated redaction, use a purpose-built workflow with an independent verification step.

That limitation is central to the comparison. A product page saying “edit text” does not, by itself, reveal whether it rewrites objects, overlays new marks, rasterizes a page, or sends the file to a conversion service. Where a competitor did not document the mechanism, this page does not invent one.

Local-only and mixed systems both have a place

HonestPDF and ClientPDF make a strong, clear local-processing claim and offer serious PDF coverage. That is good for users and raises the standard for this whole category. Their published catalogs may be a better fit than FileGizmo for a particular PDF task.

QuicklyPDF and Aservus document mixed systems. Common PDF operations can stay in the browser, while office conversion, repair, or heavier processing can use server components. That design can deliver capabilities that are difficult to reproduce faithfully in a browser. It also means the user must check the boundary of the selected tool instead of applying one privacy statement to the entire site.

iHatePDF credits both sides on its current homepage. It advertises a browser mode for client-side processing and says its server-processed files are deleted immediately. Its 35+ catalog includes specialist jobs FileGizmo does not currently offer. For a document whose policy permits that route, capability can matter more than a local-only architecture.

Common questions

Which browser PDF tools keep every file on the device?
HonestPDF, ClientPDF, and FileGizmo state that their ordinary PDF processing runs in the browser. QuicklyPDF documents a mixed design. Aservus says it processes locally when possible and uses encrypted servers for heavy tasks. iHatePDF advertises a browser mode and also documents server processing. Check the active mode before using a sensitive file.
Can FileGizmo change text that is already in a PDF?
It can replace selectable text visually while matching the detected size, family, weight, and slant. It paints over the old wording and draws the replacement. It does not rewrite the PDF content stream.
Does flattening a FileGizmo edit remove the old wording?
Yes, for corrected pages. The flatten option exports those pages as images, so the original text is no longer present there. The tradeoff is that text on those pages is no longer searchable or selectable.
Why are some comparison cells marked not documented?
A missing statement is not proof that a feature is absent. When the checked primary source did not describe existing-text behavior or underlying-content removal, this comparison records that uncertainty instead of guessing.

Primary-source receipts

All vendor pages were checked on 8 August 2026. Offers and implementation details can change, so the linked source controls when it conflicts with this summary.

  • HonestPDF homepage: named catalog, local processing, account policy, and offline claim.
  • QuicklyPDF maker submission: published operations, mixed client/server architecture, one-hour deletion, and planned form tools.
  • iHatePDF homepage: 35+ catalog, Editly text editing, browser mode, server path, and deletion statement.
  • Aservus homepage: named tools, local-when-possible policy, heavy-task server path, and one-hour deletion.
  • ClientPDF homepage: 28-tool claim, local processing, offline use, sanitize, and redaction.