UseToolSuite UseToolSuite

Excel Converter

Convert an Excel or CSV spreadsheet to CSV, JSON, PDF, or Excel — upload once, pick the output, with per-format options. Free, private, browser-based.

CSV, JSON, PDF & Excel output Per-format options preserved Runs offline in your browser No upload — files stay local

Drop an Excel file (.xlsx, .xls) or a .csv here, or click to select

Convert to CSV, JSON, PDF, or Excel — all in your browser

100% Private No Upload

Convert a spreadsheet without opening Excel — or uploading it

The Excel Converter reads a real .xlsx, .xls, or .csv file and exports it as CSV, JSON, PDF, or back to Excel — all in your browser. Spreadsheets are where the sensitive data lives: customer lists, payroll, financials. Converting them should not require handing the file to a stranger's server, and here it never does.

Each format keeps its own options

CSV export handles the real-world locale mess — a delimiter selector (Turkish, German, and French Excel expect semicolons) and an Excel-safe UTF-8 BOM toggle so accents survive. JSON export lets you choose the shape (array of objects vs a 2D grid), whether the first row is a header, whether to include all sheets, and pretty-printing. PDF export paginates every sheet as a printable table.

Where the data goes next

After converting, the CSV Viewer & Editor lets you inspect and clean rows, JSON ⇄ CSV reshapes flat data for APIs, and JSON to Excel rebuilds a workbook from JSON when you need to go the other way.

One spreadsheet, three exits — and a way back

A spreadsheet leaves your hands in different formats depending on what happens next: as a PDF when it’s a finished invoice or report for a human to read, as CSV when a CRM, bank, or database import needs a flat file, and as JSON when code will consume the rows. This converter covers all three from one upload — and accepts a CSV going the other way, rebuilding a real .xlsx workbook from it. Each direction keeps its own options: delimiter and Excel-safe UTF-8 for CSV, shape and multi-sheet export for JSON.

Preparing a spreadsheet for clean output

The quality of any spreadsheet conversion is decided mostly inside the spreadsheet before you convert. Five minutes of preparation prevents the classic ugly results:

  1. Delete or hide scratch columns — working formulas, lookup helpers, and notes columns don’t belong in the distributed document.
  2. Make the first row a real header — it becomes the table header in the PDF and the field names in JSON; a title banner merged across cells breaks both.
  3. Format numbers as you want them seen — currency symbols, decimal places, and thousands separators carry over from the cell formatting in the PDF; CSV and JSON export the underlying values.
  4. Resolve merged cells — merges that span many rows or columns are the single most common cause of misaligned tables in every output format.
  5. Check for stray data — a forgotten value in column AZ silently widens the PDF and adds a phantom field to the JSON.

When PDF is the right format for a spreadsheet — and when it isn’t

Convert to PDF when the document is final: invoices, reports for clients, price lists, sign-off sheets. The PDF freezes layout, prevents accidental edits, and renders identically on every device — exactly what you want for distribution.

Keep it as XLSX when the recipient needs to work with the data: filter it, total it, or feed it into another system. Sending a PDF of data someone will retype is a small act of cruelty; send both formats when in doubt. For machine-to-machine handoffs, the CSV and JSON exports beat both — that’s precisely why they live in the same tool.

A practical invoice-and-report workflow

Freelancers and small teams use this converter as the last step of a no-software billing pipeline: maintain the invoice or monthly report as a spreadsheet template, fill in the period’s numbers, convert to PDF here, and email the result. Because conversion happens locally, financial figures never touch a third-party server — relevant when the spreadsheet contains client rates, salaries, or unreleased revenue numbers. The same pattern works for the data directions: export the month’s transactions to CSV for the accountant’s import, or to JSON when the numbers feed a dashboard. Spreadsheet as the working copy; PDF, CSV, or JSON as the published artifact.

Excel Converter works with your documents right here in the browser — nothing is uploaded to a server. It's one of the free Document & PDF Tools on UseToolSuite. Below you'll find a step-by-step guide, answers to common questions, and related tools.

Last updated

How to Use This Tool

  1. 1

    Drop your spreadsheet

    Select an .xlsx, .xls, or .csv file. It is read entirely in your browser — nothing is uploaded.

  2. 2

    Pick the output and options

    An Excel file converts to CSV (delimiter, UTF-8 BOM), JSON (shape, header, all sheets, pretty print), or a paginated PDF. A CSV converts to a real .xlsx workbook or JSON.

  3. 3

    Copy or download

    Text outputs preview live and update as you change options; copy them to the clipboard or download the converted file.

How helpful was this tool?

Click to rate

Embed this tool on your site

Paste this snippet into any HTML page or blog post to embed a live, fully working copy of Excel Converter. Free for any use.

Key Concepts

Essential terms and definitions related to Excel Converter.

XLSX

The default XML-based spreadsheet format used by Microsoft Excel since 2007, internally a ZIP of XML parts a browser can read without Excel.

Delimiter

The character separating CSV columns — a comma in most locales, a semicolon in Turkish/German/French Excel where the comma is the decimal mark.

UTF-8 BOM

A few invisible bytes at the start of a file that tell Excel it is UTF-8, so accents and non-Latin characters display correctly.

Frequently Asked Questions

What can I convert my spreadsheet to?

From an Excel file (.xlsx/.xls): CSV, JSON, or a paginated PDF. From a CSV file: a real .xlsx workbook or JSON. Upload once and switch the output with the selector — each format keeps its own options.

My CSV opens with everything in one column in Excel — why?

That is a delimiter/locale mismatch. Turkish, German, and French Excel expect a semicolon, not a comma. Pick the matching delimiter, and leave the UTF-8 BOM option on so accented characters survive when Excel reopens the file.

Which JSON shape should I choose?

Array of objects turns each row into a keyed record using the header row — ideal for APIs and databases. 2D array keeps the raw grid when column order matters more than names. Enable All sheets to export a multi-tab workbook as one object keyed by sheet name.

Are Excel formulas kept?

No. A spreadsheet file stores the calculated values, and those are what get converted — the formulas behind them are not carried into CSV, JSON, or PDF output.

How do I stop columns from being cut off in the PDF?

Reduce the content before converting: hide helper columns you don't need in the output, shorten verbose headers, and split very wide sheets into two logical tables. Wide financial models simply contain more columns than a printable page can hold — the converter scales what it can, but a 30-column sheet will always be more readable as two 15-column PDFs. Or side-step the problem: export to CSV or JSON instead, where page width doesn't exist.

Why does my exported CSV open as one column in Excel?

A delimiter/locale mismatch. Excel installations in locales where the comma is the decimal separator — Turkish, German, French among others — expect semicolon-delimited CSV and refuse to split on commas. Export with the semicolon delimiter option for those locales, and keep the UTF-8 BOM option on so accented characters survive the round trip.

Which JSON shape should I export — objects or a 2D array?

Array of objects when each row is a record and the header row names the fields — that's what APIs, database seeders, and JavaScript apps consume directly. The 2D array keeps the raw grid of values, which is better when column order matters more than names or the sheet has no clean header row. Numbers stay numbers and dates become ISO strings in both shapes, so the JSON needs no cleanup pass.

Should I think portrait or landscape for spreadsheet PDFs?

Think in terms of your data's shape: tables are almost always wider than they are tall, so the PDF output uses landscape to fit more columns. Portrait suits only narrow lists (a few columns of names, dates, amounts). If recipients will print the PDF, match the orientation to the paper they'll use.

Troubleshooting & Technical Tips

Common errors developers encounter and how to resolve them.

PDF columns are cut off on a wide sheet

The PDF is generated in landscape to fit more columns, but very wide sheets can still overflow. Hide unneeded columns in the source spreadsheet, or export to CSV/JSON instead where width is not a constraint.

Accented characters look garbled after opening the CSV

Keep the UTF-8 BOM option enabled — it tells Excel the file is UTF-8. Without it, Excel on some locales misreads accents.

Related Tools