Convert a bank statement to CSV without uploading it anywhere

A bank statement contains more than a list of purchases. It may include your name, address, account details, salary, transfers, merchant history, and current balance. That makes the way a converter handles the file worth checking before you use it.

What an upload-based converter asks you to trust

With a typical online converter, selecting a file starts an upload to a server. The service must receive and process the complete statement before it can return a spreadsheet. A promise such as "files are deleted after conversion" may limit storage time, but it does not change the fact that the document was transmitted and handled outside your computer.

That processing can involve logs, temporary storage, backups, or a separate OCR provider. None of those practices automatically makes a service unsafe, but they expand the number of systems and policies you must trust. For a document with detailed financial information, avoiding the transfer altogether is a simpler privacy boundary.

How local browser conversion is different

A client-side converter runs the parsing code in the browser tab you already have open. In Statement2CSV, JavaScript reads the selected file through the browser's local file API. pdf.js extracts the text, and the transaction parser builds the rows in memory on your device. The PDF itself and the extracted transaction data are not sent to a Statement2CSV server.

The page still needs an internet connection to load the site and its required files the first time. After it has loaded, you can disconnect and convert a statement. The conversion continues because the work happens in the tab, not on a remote machine.

Verify the claim instead of taking it on trust

You can check the behavior with tools built into Chrome, Firefox, Edge, and Safari:

1. Open the converter, then open the browser's developer tools.
2. Select the Network tab and clear the existing request list.
3. Choose a statement and wait for the preview to appear.
4. Look for a new request that transfers your PDF or a large request body. There should not be one.

For an even simpler test, load the converter first, switch your device to airplane mode or disable its network connection, then select the PDF. A local converter can still produce the preview and CSV while offline. If you inspect network traffic, remember that loading the page itself fetches normal site assets. The relevant point is that choosing the statement does not trigger a file upload.

The tradeoff: no server-side OCR

Keeping the entire process local has one important limit. Statement2CSV does not send pages to an OCR service, so it cannot read image-only scans, photographs, or screenshots. It needs a text-based statement PDF downloaded directly from your bank. Test by selecting a transaction description in your PDF viewer. If you can copy the words, the file is likely suitable.