No Fuss PDF
Fill, sign, merge and convert PDFs without the file leaving your device.
Operated by Rust Solutions Ltd
Where your files are processed
Files stayed on your device when we tested
We supplied a test PDF on 16 October 2026 and no file left the device. Our check confirmed the tool actually ran: The tool produced a file for download (probe-filled.pdf), so it demonstrably ran.
TESTED ON TWO KINDS OF DOCUMENT, NOT TAKEN ON TRUST. A text based PDF carrying a marker, and a second file that is a single image with no text layer at all, were each put through the fill tool in a browser. Both rendered locally, accepted typed text and produced a filled PDF for download, so the tool demonstrably processed them. Nothing left the device: no marker appeared in any request and every request went to nofusspdf.com. The only traffic was eight named first party events carrying no document content. The submitter asked for this to be recorded as their claim until independently tested; it has now been tested, so it is recorded as a finding. TESTED AGAIN ON 1 OCTOBER 2026, ON A FORM BUILT HERE, WHICH ASKED A DIFFERENT QUESTION. The first test established that the file never leaves the device. The second asked what the finished file contains. The form was a single image with no text layer, which yields no text at all when read. A marker typed into it through the live tool came back out of the downloaded file as selectable text, and nothing from the scanned image came through, so the answer a reader types is readable afterwards and the words already printed on a scan are not. Every one of the twenty two requests went to nofusspdf.com and none went anywhere else.
What it does
No Fuss PDF is a set of browser tools for the ordinary document jobs: fill a form, sign, merge, split, extract pages and convert between PDF and images. A source file does not need a text layer, because the fill tool adds one. The fill tool places visible text, dates, checks and signatures on top of the page, so it works on scanned and flattened forms that have no fillable fields. The files, the entered answers and the signature stay in browser memory, and nothing about the document is sent anywhere. It is free, needs no account and adds no watermark.
Best for: Someone holding a scanned or flattened form that has no fillable fields, who needs to type on it and sign it and would rather not send the document to a server. Also anyone who wants to fill, merge or convert a PDF in one place without creating an account first.
Worth knowing: The signatures are visible page overlays, not cryptographic digital signatures, so they carry no certificate and prove nothing about who signed. There is no redaction, no OCR, no editing of the document's own text and no support for creating new interactive form fields, and password protected PDFs are refused. Filling adds a new text layer over the page. It does not create an interactive form field and it does not read the words already in the scan, so an answer you type is selectable and extractable while the printed words in a scanned form stay image only. Tested here on 2026-10-01: an image only form with no text layer was filled through the live tool, the answer typed into it came back out of the downloaded file as selectable text, and nothing from the scanned image did. An example the operator publishes returns the same result. A reader who needs the original scanned words to be searchable needs OCR, which this tool does not do. The site sends a small set of anonymous usage events, described in detail on its privacy page and confirmed by testing; they contain nothing from your document. The test narrative is recorded as a short result with an evidence link: tested tool, build, date, fixtures, output inspection and network scope, with the original evidence preserved before any historical assertion is reused, because this documentary audit did not reproduce it. A fill-tool observation is not generalised into independent verification of every tool, a future version or all possible transmission, and same-origin traffic can carry data, so destination names alone are not evidence of no upload. No document upload does not mean no network requests or browser storage. A visible signature does not provide cryptographic identity verification, and its evidential meaning is outside this product test. Unknown file limits stay unknown.
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
- Website
- nofusspdf.com
- Requires an account
- No
- Watermark on the free tier
- No
- Maximum file size
- Not verified
- Batch processing
- Not verified
- Data residency
- Not verified
- Open source
- No
- Self-hostable
- No
- Licence
- Not verified
- Redaction
- No redaction feature
- Programmatic access
- None
- Last availability check
- Responded in 298 ms 16 October 2026
Checked automatically by our own runner, not reported by the vendor. 100% of our last 22 checks got a response.
What the redaction verdict rests on
From the vendor's own documentation, read 29 September 2026. Not tested by us.
“We do not offer redaction.”
What that does not establish: There is no redaction feature. The operator states this in their submission of 2026-09-29 and nothing in the tool contradicts it. The point is worth stating rather than leaving implicit, because this product draws visible marks on top of a page as its normal way of working, which is the mechanism that makes a bad redaction fail. A reader should be clear that a visible overlay here is a form answer, not a redaction, and that the tool makes no redaction claim at all.
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.
-
“Fast, simple PDF tools. No account, no upload, no watermark, and no fuss.”
Checked by us — the source says this Read 29 September 2026
All three hold in the sense that matters here. No account was created or offered at any point and the tool worked immediately, which is the strongest available reading of no account. No upload occurred. No watermark was added by the tool to the file it produced. The no account part is a positive finding, because we completed a task without one; the no watermark part is a weaker one, because we did not open the downloaded file to inspect it, so it rests on the tool offering no watermarking feature and on the download completing cleanly rather than on an inspection of the output.
Standing: Not re-read against the live source
Check it yourself: the source, the SHA-256, and how we checked
- From
- the text a browser renders
- SHA-256
- 0b1302a6f0509f14976efe9f8fa0d6c9a7308e53426a469580572e0251028fb5
How we checked: The sentence was found on 2026-09-29 in the text the page renders, read with headless Chrome because the site returned almost nothing to a plain fetch at the time of the read. It returns static HTML now, so that has changed since. The three claims inside it were then exercised: the fill tool was used from a fresh browser context with no account and no sign in, on two documents, and it produced a filled PDF for download with no watermark applied by the tool. sourceHash is the SHA-256 of the rendered text, held as p13-nofusspdf-home.txt.
-
“Your PDF, form text and signature remain in your browser and are never uploaded to No Fuss PDF.”
Checked by us — the source says this Read 29 September 2026
Confirmed. Both documents rendered locally, accepted typed text, and produced a filled PDF for download, so the tool demonstrably processed them. No marker appeared in any request and every request went to nofusspdf.com, 22 of them, so no third party was contacted. The eight events the page sent carried no filename, no document text, no metadata and no signature data. The signature part of the claim is not something this test touched, because no signature was created; it is recorded as the vendor's statement.
Standing: Not re-read against the live source
Check it yourself: the source, the SHA-256, and how we checked
- From
- the text a browser renders
- SHA-256
- f42f6f22dc317c5af669847f67bd5d7fb35cfa273e6a8372899bd70557ac5260
How we checked: Tested on 2026-09-29 with two purpose built documents, one carrying a marker string in its text layer and one that is a single image with no text layer, while every request the page made was recorded. The marker is the instrument: finding a unique string from the file in a request body proves the document was transmitted. The detector was proved before use with its own three control self test. The page text was read with headless Chrome, held as p13-nofusspdf-fillpdf.txt.
-
“The source files and generated files are not sent to No Fuss PDF's servers.”
Checked by us — the source says this Read 29 September 2026
Confirmed, and this is the claim the whole record is built on. The page explains the mechanism rather than asserting the outcome, naming PDF.js for rendering and pdf-lib for filling, signing, merging and splitting, all of which run in browser memory, and the testing agrees with it. No document bytes, filename, metadata, entered text or signature appeared in any request. The privacy page also says plainly what IS collected, and that part held up too: see the telemetry claim below.
Standing: Not re-read against the live source
Check it yourself: the source, the SHA-256, and how we checked
- From
- the text a browser renders
- SHA-256
- e31549f1a30fb15c5c483d0f4d2f33b26d7293c30c2ffed36492c5ceb10ae079
How we checked: Read on 2026-09-29 with headless Chrome, held as p13-nofusspdf-privacy.txt, and then tested rather than taken on trust. Two marked documents were processed to a completed download while every request was recorded, including the bodies of every POST. The privacy page's own disclaimer was checked against what the page actually did.
-
“No Fuss PDF is operated by Rust Solutions Ltd. Rust Solutions Ltd is the data controller for the limited operational data described on this page.”
Checked by us — the source says this Read 29 September 2026
The operator is named on the privacy page as Rust Solutions Ltd, and this is the name now recorded on this record as the owner. The submission did not name it: it signed off as the No Fuss PDF team and came from a personal address. Because this index records entities rather than individuals, the privacy page is the better authority and the name it gives is the one used. The submitter has been asked to confirm it on 2026-09-29 and had not replied when this record was written, so if they correct it the owner field changes.
Standing: Not re-read against the live source
Check it yourself: the source, the SHA-256, and how we checked
- From
- the text a browser renders
- SHA-256
- e31549f1a30fb15c5c483d0f4d2f33b26d7293c30c2ffed36492c5ceb10ae079
How we checked: Read on 2026-09-29 with headless Chrome, held as p13-nofusspdf-privacy.txt. The finding is a discrepancy rather than a confirmation, and it is recorded because the operator field on this record depends on it.
-
“These events contain no data from or about your document and no personal identifying data.”
Checked by us — the source says this Read 29 September 2026
Confirmed, and the disclosure is unusually good. Eight events were sent across a completed fill and download: page_view, tool_started, pdf_selected, fill_item_placed, fill_text_entered, download_started, tool_completed and download_completed. Each carries the tool name, anonymous visitor and session identifiers, device class, browser family and the acquisition source, with a duration bucket on the two that measure time. The fill_text_entered event does NOT contain the text that was entered. No event contains a filename, document metadata, page content or the marker. The page's exclusion list was therefore accurate in every particular we could test, including one case the reader would most want to be true.
Standing: Not re-read against the live source
Check it yourself: the source, the SHA-256, and how we checked
- From
- the text a browser renders
- SHA-256
- e31549f1a30fb15c5c483d0f4d2f33b26d7293c30c2ffed36492c5ceb10ae079
How we checked: Read on 2026-09-29 with headless Chrome, held as p13-nofusspdf-privacy.txt, and then checked against every event the page actually sent during a complete fill and download. The bodies of all POST requests were captured, and the text typed into the document was a known string, so its absence from the events could be tested directly rather than assumed.
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.
Related reading
- Which PDF tools keep your file on your machine — what we count as processing on your own device.