CSV converter
Convert local supplier tables, text PDFs and bank CSV files into the format you need. Your file stays in your browser.
Converted records
2 data rows ready
Source rows
2
Output rows
2
Columns
3
Review the preview and warnings before importing the downloaded file.
2 data rows ready. Cell values remain strings without type conversion.
Transaction reconciliation
Valid transactions
0
Rows to review
0
Credits
$0.00
Debits
$0.00
Net amount
$0.00
Selected PDF page
Row and column preview
Converted file
Choose the input and output format
This free CSV converter reads local supplier tables and creates a downloadable row-based file. Choose the input format, select its records and check the output preview.
A supplier’s semicolon TXT export needs the semicolon delimiter. Text-to-CSV conversion reads those separators into columns and writes quoted CSV fields. Renaming the file leaves its original contents unchanged.
The default example contains two products and three columns. Quotes keep “Café, cup” in one cell. The second product’s note contains a line break inside the same record.
File encoding applies to local text bytes. Choose Windows-1252 for a matching supplier export or UTF-8 for Unicode text. Pasted text is already decoded.
CSV output uses your chosen separator. TSV always uses tabs. Both use UTF-8 and quote every cell under the common quoting rules in RFC 4180.
Preserve product identifiers
The converter keeps identifiers as text. The example’s GTIN 0012345678901 retains its leading zeros, and long numeric text stays intact.
CSV quoting does not set a spreadsheet’s column types. Import identifier columns as text when opening CSV. XLSX output writes every cell as text, including formula-looking values.
Formula protection is optional for CSV and TSV. It adds an apostrophe before values beginning with a formula character, including negative numbers. Leave it off for an exact text round trip.
A workbook may already store a rounded numeric identifier. Converting it cannot recover the missing digits. Compare those identifiers with the supplier’s original text source.
Check the converted rows
Compare source and output row counts before importing. The counts exclude a selected header row. A quoted line break belongs to its cell and does not create another record.
Inspect the preview’s row arrays for empty trailing cells, shifted columns and broken quoting. Uneven records remain intact in CSV, TSV and JSON row arrays.
JSON objects and XML require unique field names and equal column counts. Resolve the warning or choose row arrays when the original shape needs to remain unchanged.
Load the downloaded CSV or TSV back into this converter with its matching delimiter. Compare the record counts, identifiers and embedded line breaks before importing into your store.
Use the guide to product feed optimisation to map the converted columns to your catalogue’s required fields.
Convert JSON to CSV
Choose JSON and enter the product array’s path. For a document with a products array, use products. Use $ when the document itself is an array.
Load the JSON example to map sku=sku, name=details.name and stock=stock. Its two products become two CSV rows. The second product’s missing stock field appears as “(missing)”.
Each mapping line names an output header and its source field. Nested objects use dot-separated paths. Nested arrays stay together as JSON text in one cell so variants do not become extra products.
CSV-to-JSON objects use the selected header record as field names. Cell values remain strings. A flattened details.name column stays a literal field name on export, so arbitrary nesting is not restored.
Convert excel and numbers tables
Choose a real XLS, XLSX or Apple Numbers file, then select its worksheet or table. Enter a range such as A1:D20 to exclude notes outside the catalogue.
For example, open a supplier’s Stock.numbers workbook and select its Products table. Check that the first row contains sku, name and stock before choosing CSV output.
The Numbers reader exposes each table as a separate worksheet choice. “Number to CSV” in this context means the Numbers application.
Displayed text keeps saved number formatting, such as a code shown as 000123. Stored values expose the underlying number, such as 123. Text cells retain their exact content in either mode.
The converter extracts saved cell values without recalculating formulas. It reports workbook conversion losses, including merged cells. Data-only output omits formulas, charts, macros and embedded objects.
Choose Excel workbook for a genuine XLSX download. Its identifier columns contain text cells. The workbook contains the selected data, with one Converted worksheet.
Convert XML records and HTML tables
For XML-to-CSV conversion, choose the repeated product path, such as catalog.product. Map sku=@sku for an attribute and name=details.name for a nested field.
Choose products at the product level when each product contains several variants. Selecting the variant element creates variant rows instead. Nested repeated values stay in one cell as JSON text.
For CSV-to-XML output, select the root and record names and enter one XML field name per column. The converter escapes ampersands and angle brackets. Flattened columns cannot reconstruct arbitrary source nesting.
For HTML-to-CSV conversion, paste a table or choose a local HTML file. Select its table number. The converter reads inert cell text and never runs embedded scripts.
Merged cells expand into the table grid with empty covered cells. Review merged-cell warnings and repeated header rows before downloading. Tables nested inside cells need a separate table selection.
Extract a text PDF table to CSV
Choose a local PDF with selectable text, then select its page and table area. The free PDF-to-CSV conversion runs in your browser.
PDF text has page positions instead of CSV fields. Column boundaries mark positions from the page’s left edge. To join wrapped descriptions, adjust the row boundaries measured from the top.
Preview the selected area, then edit the proposed row arrays when a merged cell or wrapped description needs correction. Repeated headers and text crossing column boundaries trigger warnings.
Confirm that you checked every row before downloading. Image-only scans show a message explaining that OCR is required. They do not produce an empty or invented table.
Prepare bank CSV transactions
Choose Bank CSV, QIF or OFX output for a downloaded business-bank CSV. Map its transaction date and description, then choose a signed amount or separate debit and credit columns.
Signed amounts use positive credits and negative debits. Separate debit and credit columns use positive amounts in one column per row. Choose the source date convention explicitly for ambiguous day/month dates.
Load the bank example to see a $12.50 debit and a $30.00 credit. Two source transactions produce two output transactions with a $17.50 net amount.
Enter the statement’s transaction count and net amount. Both must match the parsed records before saving. Invalid dates and amounts appear with their source row numbers and block the download.
The converter keeps every transaction for review. It retains zero amounts with a warning because Xero’s import guidance identifies them as invalid for manual import.
Convert CSV to QIF online
Choose QIF output after mapping and reconciling the bank rows. Select Bank, Credit card or Cash and choose the date convention expected by the receiving application.
For the two-transaction bank example, the QIF contains a -12.50 amount for stock and a 30.00 amount for sales. Each transaction ends with a caret record separator.
The file uses the banking fields in the archived Intuit QIF reference. Optional payee and memo columns can be mapped separately.
Xero accepts QIF, OFX and CSV statement imports. Review the imported dates and signs before completing the import. Quicken’s QIF support depends on the account and application version.
This browser conversion needs a downloaded file and no bank login. It covers banking transactions. Investment transactions require a different record format.
Convert CSV to OFX
OFX output creates an XML banking statement using OFX Banking 2.3. Enter the bank identifier, account number, ISO currency code and statement period.
Enter the closing balance from the statement. The period must contain every mapped transaction. The converter validates the required fields and generated XML before enabling download.
OFX records carry transaction dates, signed amounts and unique transaction IDs inside a statement structure. A CSV with an .ofx extension does not have that structure.
Map a supplied transaction ID when it is unique. Otherwise a stable local ID comes from the date, exact cents, description, payee and memo, plus an occurrence number.
Identical same-day transactions remain separate. Re-exporting the same rows keeps their IDs. Keep original bank IDs across overlapping statements when available, since locally generated IDs cannot establish identity across different source selections.
Review the receiving application’s imported transaction count and total against the statement before saving. Import support and duplicate handling depend on that application’s accepted OFX version.