Skip to content

Local PDF tool - browser processing

Redact a bank statement PDF privately

Redacting a bank statement privately means removing account numbers, transactions, and addresses in your browser so a lender or landlord sees only what they need. You select the sensitive details, apply secure redaction, and export — we never receive a copy, because the statement never leaves your device.

Redact the statement locally See the proof

0 bytes sent proof

What the widget measures

The panel counts what leaves your browser after you choose a file. The site's own scripts and fonts load like any web page — what you will never see is a request carrying your PDF. Check it here, or open your browser's Network tab and see for yourself.

0 bytes of your document sentStarts measuring when you choose a file on a tool page
Document request bodies
0 bytes
App network after file open
0 bytes
Processing engine
Browser WASM worker

The number is scoped to request bodies after you choose a document. App assets such as JavaScript, WASM, and fonts can still load; those are not your PDF bytes.

Verify it yourself
  1. Open DevTools, then the Network tab.
  2. Choose a PDF in the tool and complete the action.
  3. Filter for fetch or XHR requests; document processing should not create a request carrying your file.

Stronger check: load the tool page first, then disconnect from the network before choosing the file. Already-loaded tool code can continue processing locally, but a first visit still needs the site assets.

Local vs. online

How local processing compares

Doing this in Lemmafour keeps the file on your device. A typical online PDF tool uploads it to a server first — here is the practical difference:

  Typical online PDF tool Lemmafour
Where your file goes Uploaded to the provider’s servers Stays in your browser — never uploaded
Works offline No — it needs a round trip to their server Yes, once the page has loaded
Account or sign-up Often required Never — no account, no email
What they keep afterwards Your file sits on their servers until they delete it Nothing to keep — it never left your device

Steps

How to do it in Lemmafour

  1. Choose Redact the statement locally.
  2. Open the bank statement PDF.
  3. Use Secure redaction in text or area mode.
  4. Redact full account numbers, routing details, irrelevant transactions, addresses, and reference codes.
  5. Apply redactions, export, and search/select text in the output to check the removed areas.

Expert note

Statement tables need repeated checks

Financial PDFs often repeat the account number in page headers, transaction descriptions, footer references, and embedded statement metadata. If you split the statement first, each output must still be checked because repeated headers can survive on every page. Keep the unredacted original separate from the shared copy.

FAQ

Questions people ask before using this tool

Can I leave the balance visible?

Yes, if the recipient needs it. Redact only unnecessary details so the document still supports the request.

Should I split before redacting?

Split first if the recipient needs only some pages, then redact the smaller output.

Does Lemmafour store my statement online?

No. Recent outputs may stay in this browser until cleared, but they are not uploaded for processing.

Related private PDF workflows

Keep working locally

Split a bank statement PDF without it leaving your device Split a bank statement PDF into selected page ranges locally before sharing only the pages needed. Redact a PDF without uploading Use secure redaction mode locally in your browser and verify that redacted text is not recoverable. Extract PDF pages without uploading Pick pages or ranges from a PDF and save them as a new local PDF in your browser. Compress a PDF locally Reduce PDF file size right in your browser — the file never goes to a server to be compressed. PDF tool hub Browse the shipped local PDF tools.