Skip to content
dialegein

DocHub

Browser PDF editor and e-signature tool wired into Google Drive and Gmail.

Jobs Edit — field and form preparation; not editing original PDF text Sign Merge Protect

Where your files are processed

Reported to upload your files

The vendor states that files are uploaded to their servers. We have not independently tested this.

Documents are uploaded and saved in your account, and the vendor's help centre states they are stored in encrypted AWS S3 storage until you delete them. The editor runs in the browser but the document does not stay on your machine.

What it does

DocHub is a browser-based PDF editor and e-signature service. You upload a PDF or import from Google Drive, Dropbox or OneDrive, then edit embedded text, annotate, add fillable form fields, merge, split or reorder pages, and sign it or send it for signature with tracking. Uploaded documents live in your DocHub account on its storage until you delete them. Free accounts can edit, sign and share within daily and monthly limits.

Best for: Google Workspace-centric individuals and teams that need to fill, edit and e-sign PDFs in a browser without installing desktop software.

Worth knowing: Cloud only: files are uploaded and stored until you delete them, free accounts are capped by daily and monthly limits, and premium tools require DocHub Pro. Its whiteout and redact tool covers content rather than removing it. Redaction behaviour is not independently tested and the vendor documentation conflicts: the linked help article describes movable whiteout annotations, while the current pricing matrix describes permanent text and image removal. Neither marketing language nor reversibility inside the editor establishes what an exported PDF contains, so an applied and exported file would need extraction and object inspection before a Removes or Covers verdict is assigned. Current pricing describes a shared three-use monthly allowance across core free features rather than unspecified daily or monthly limits, and Pro documents Bulk Send, so bulk signing is vendor-supported with a plan restriction rather than general PDF batch processing. Document-password protection appears in the enterprise Site License comparison, so Protect is qualified by operation and plan. Cloud storage and optional AI workflows are vendor-reported.

Details, and where each comes from

Vendor statements, our own reading of their pages, and the things nobody has established yet, each answered separately. Where we have not confirmed something it says so rather than guessing, and a row nobody has established is greyed out.

Versions covered
Web · iOS · Android
Website
dochub.com
Requires an account
Yes
Free tier
Yes
Watermark on the free tier
Not verified
Maximum file size
Not verified
Batch processing
Not verified
Data residency
Not verified
Open source
Not verified
Self-hostable
Not verified
Licence
Not verified
Redaction
Covers it — content is not removed
Programmatic access
None
Last availability check
Responded in 114 ms 16 October 2026

Checked automatically by our own runner, not reported by the vendor. 100% of our last 30 checks got a response.

What the redaction verdict rests on

From the vendor's own documentation, read 22 September 2026. Not tested by us.

“The Whiteout Tool allows you to easily cover up and erase content on a PDF document. … lets you frame a box over any area of your document you want to cover or erase with whiteout. … This will create a boxed annotation window that is filled with white space.”

What that does not establish: The vendor’s own help article, not a test we ran. The wording decides the verdict: the tool creates a boxed ANNOTATION filled with white space, and an annotation is something added to the page — nothing here says the covered characters leave the file. The same article notes that the black variant ("Redact") requires the paid Pro plan while whiteout is available without it, so which of the two a reader gets depends on their plan.

https://help.dochub.com/knowledge-base/document-editing/adding-whiteout-or-redactions-to-your-document

What the vendor says

Claims are labelled rather than repeated as fact. Where we have checked something ourselves, it says so and shows when. Checked means we read the vendor's own page and it says what we recorded — not that we tested the behaviour, unless the note says we did.

  • “DocHub is encrypted end-to-end, and files are stored in AWS (Amazon Web Services) using encrypted S3 storage.”

    Checked by us — the source says this Read 22 September 2026

    Confirmed verbatim: "DocHub is encrypted end-to-end, and files are stored in AWS (Amazon Web Services) using encrypted S3 storage." One part of that sentence is supported on the page and one part is not, and a reader deserves to know which. The storage half is stated plainly and consistently. The "end-to-end" half rests on transport encryption: the only evidence the article offers is "The details of the SSL encryption can be seen by clicking the green lock icon in your browser when visiting DocHub". TLS protects the connection between a browser and a server; end-to-end encryption in its ordinary sense means the provider cannot read the content, and nothing on the page claims that or describes a scheme that would achieve it. Recorded as the vendor's wording rather than as a finding about the product, because we have not tested the service — but the phrase overstates what the page itself evidences, and this is the kind of wording a reader is most likely to take at face value.

    Standing: Re-read and matched byte for byte

    Check it yourself: the source, the SHA-256, and how we checked
    From
    the text a browser renders
    SHA-256
    042839529509a5152f6662bc1c248c7621786e9d7bdda8db57f6f010408d5203

    How we checked: Re-verified verbatim on 2026-09-22: https://help.dochub.com/knowledge-base/security-privacy-compliance-and-data-retention/how-secure-is-dochub-to-use re-rendered in headless Chrome with scripts/render-page.mjs and the claim's wording found in the rendered text. Originally verified on 2026-09-21. sourceHash is the SHA-256 of the re-rendered text, held as rv-help-dochub-com-knowledge-base-security-privacy-compliance-a79f7f4b.txt.

    What this hash proves, and what it does not

  • “All documents you upload directly to DocHub will be saved in your account permanently without an expiration date unless you manually delete the file from DocHub.”

    Checked by us — the source says this Read 22 September 2026

    Confirmed verbatim: the article's answer opens with the claim exactly. It is recorded as confirmed rather than partial because the exception the page then describes falls outside the claim's own scope, and that distinction took reading to establish. The claim covers "documents you upload directly to DocHub"; the page's "one exception to this automatic save rule" is for a free account opening a file from Google Drive or Gmail through Open With, where nothing is annotated and Save in DocHub is never pressed — "the file will only be stored in DocHub for 7 days and then be automatically deleted", with a days-left label shown and an Activity Feed entry reading "DocHub Maintenance Server" and "Destroyed". A direct upload is not that case, but a free-account reader is, and this is the fact they need from this page. Two more details belong with it: manual deletion is irreversible, and the page states "We do not retain any backup copies as part of our privacy and data retention policy", which is a stronger commitment than the claim and one that makes the manual delete path final. Recorded as the vendor's description; we have not tested the service and no control was run.

    Standing: Re-read and matched byte for byte

    Check it yourself: the source, the SHA-256, and how we checked
    From
    the text a browser renders
    SHA-256
    2c4d3aa6d344ff0940655bde4ef09abf72cde80e006170eac7e45f99afc51d06

    How we checked: Re-verified verbatim on 2026-09-22: https://help.dochub.com/knowledge-base/security-privacy-compliance-and-data-retention/will-dochub-ever-automatically-delete-my-pdf-documents re-rendered in headless Chrome with scripts/render-page.mjs and the claim's wording found in the rendered text. Originally verified on 2026-09-21. sourceHash is the SHA-256 of the re-rendered text, held as rv-help-dochub-com-knowledge-base-security-privacy-compliance-3b36ef80.txt.

    What this hash proves, and what it does not

Each claim is quoted from the vendor's own pages. This section describes what we have and have not checked — it is not a judgement about anyone.

Sponsorship is distribution, not an endorsement or a promise of search rankings, AI citations, traffic, or sales. This listing is a free entry, compiled from published sources.

Visit DocHub Report a problem

How this record was put together

Editorial review.
No editor has signed this record off. That is not the same as nothing having been checked, and the lines below say what has.
Source reading.
2 claims taken from the vendor's own pages, read between 22 September 2026 and 22 September 2026.
Website availability.
The vendor's site was last checked on 16 October 2026.
Behaviour testing.
We have not run this tool ourselves, so everything here rests on the vendors’ own pages.

Sources: dochub.com; dochub.com/pricing; help.dochub.com knowledge base articles on security, data retention, editing, whiteout/redaction and mobile; legal.dochub.com.