Your bank gives you a PDF; your accounting software wants OFX. Every online PDF-to-OFX converter asks you to upload the one document that lists your account number, balance and every transaction. Filemorph does the conversion on your iPhone, iPad or Mac — the statement never leaves the device.
A PDF statement is a picture of your finances; an OFX file is the data behind it, in the format GnuCash, YNAB, Xero and most bookkeeping tools import directly. Banks that only offer PDF downloads leave you retyping every line. Filemorph reads the statement with Apple's Vision framework, finds the transaction table, and writes a standard OFX 1.02 file with a date, payee, amount and a stable ID for every transaction — the fields importers need to avoid duplicates.
Before anything is exported you see a review sheet: which columns were detected as date, description and amount, whether the statement is a checking, savings or credit-card account, the currency, and how many rows were parsed. Confirm or adjust, then export. Filemorph keeps the layout of a statement you have confirmed once — remembered on the device, with the account identifiers encrypted — so next month's statement from the same bank is a one-tap job. Password-protected PDFs work — enter the password in the sheet. Rows that cannot be parsed are counted and shown, never silently dropped.
In the app: Convert → To OFX.
CSV is just text: every finance app needs you to map columns, fix dates and guess signs on import. OFX carries typed fields — posting date, amount with the correct sign, payee, account type and a unique transaction ID — so the import is one step and re-importing the same statement does not create duplicates. Filemorph writes OFX 1.02, the version the widest range of importers accepts.
GnuCash, YNAB and Xero import Filemorph's OFX directly; so does most software that lists OFX or "Web Connect" on its import menu. Filemorph writes plain OFX 1.02 — it does not write QFX, the licensed variant some desktop products require. If your software only lists QFX, check whether it also accepts OFX (many do) before relying on this conversion.
Statements are messy: opening-balance rows, page headers repeated mid-table, amounts in parentheses, credits in a separate column, dates as 07/15 with the year only in the header. The review sheet shows what was detected and lets you correct the account type, currency, date order and sign convention before export. When a layout is ambiguous — for example every date has a day of 12 or less — Filemorph flags it rather than guessing silently. Credit-card statements have their signs flipped automatically so charges import as debits.
Yes. Unlike web converters that upload your files to a server, Filemorph converts every file locally using Apple's frameworks. Nothing leaves your device, and it works with no internet connection. This operation is part of Filemorph Pro ($29.99/year, 7-day free trial on monthly and annual plans). Requires iOS 26+.
No. The PDF is read, the table recognized, and the OFX written entirely on your device. Turn on Airplane Mode and it still works. Filemorph has no account system and no servers that ever see your files.
It requires iOS 26, iPadOS 26 or macOS 26 — Filemorph uses the document-table recognition Apple introduced in those releases. PDF to OFX is part of Filemorph Pro ($29.99/year, 7-day free trial on monthly and annual plans).
Yes, as long as the table is legible: recognition is optical, so a clean scan or a phone photo saved as PDF works. Very skewed or low-resolution scans may leave rows unparsed — the sheet tells you how many.
No. Filemorph writes standard OFX 1.02. QFX is a licensed variant, and the app does not produce it. GnuCash, YNAB and Xero import the OFX file directly.
Supported. Choose the credit-card account type in the review sheet (it is usually detected) and Filemorph writes the OFX with the correct account block and sign convention so charges import as debits and payments as credits.
On-device, no upload. Plus 300+ more file operations.
Download on theApp Store