The tools directory at /tools is Convert CSV’s searchable catalog of converters, spreadsheet utilities, and related data tools — grouped by category so you can find the right Input→Output page without guessing URLs. Browse Spreadsheet Tools, Data Converters, File Utilities, CSV Export Tools, Developer Tools, Document Tools, and Finance Tools, or type a format name into search and filter the cards in real time.

Each listing opens a focused single-purpose page rather than one do-everything uploader. That design keeps expectations clear: JSON to CSV expects JSON; CSV to SQL expects CSV. The directory itself does not transform files; it routes you to the page that will, with guides, examples, and FAQs tailored to that pair of formats.

Below you will find how categories are organized, how to pick between import and export directions, when to use an editor instead of a converter, privacy and client-side processing notes, two-step paths through CSV, finance and GIS specialty tools, and a full troubleshooting and FAQ section for navigating the catalog efficiently.

Key features

One directory covering converters and related utilities across spreadsheet, data, file, CSV export, developer, document, and finance categories.
Keyword search across titles, descriptions, and associated keywords so you can type a format name instead of memorizing paths.
Category grouping that surfaces related tools — useful when you know the domain (finance, GIS, HTML) but not the exact slug.
Direct links to single-purpose pages with format-specific documentation rather than a generic multi-format black box.
Coverage of both directions for many formats (to CSV and from CSV) so you can start from whichever file you hold.
Client-side filtering of the catalog UI — search updates without a round-trip to find the right card.
A natural jumping-off point to editors when the catalog makes clear you need cleanup rather than conversion.

About the CSV, JSON, XML, SQL, KML, HTML, YAML, GeoJSON and fixed-width text to CSV, Excel or spreadsheet-ready rows format

Import-style converters (JSON to CSV, XML to CSV, SQL to CSV, HTML Table to CSV, KML to CSV, GeoJSON to CSV, Fixed Width to CSV, and similar) accept structured or semi-structured sources and produce spreadsheet rows. Export-style converters (CSV to JSON, CSV to XML, CSV to YAML, CSV to SQL, CSV to Markdown, CSV to Excel, CSV to PDF, and similar) start from CSV and emit another format.

Spreadsheet and file utilities cover Excel bridges, HTML extraction, and cleanup-adjacent workflows. Finance tools handle OFX, QFX, QIF, IIF, and related bank or accounting exports through the finance converter hub. Document and developer tools cover presentation and code-oriented outputs such as Word, PDF, QR, HTML tables, and delimited variants.

Editors (universal /editor, Online CSV Editor, Online XLSX Editor) appear in the broader product surface as grid workspaces — use them when cell values need human edits. Converters change representation; editors change content. The directory helps you choose which class of page to open first.

How it works

The directory renders registered tools as searchable cards: title, short description, and category. Typing in the search box filters those cards by matching against titles, descriptions, and keywords entirely in the browser so results update as you type.

Opening a card navigates to a dedicated converter or hub page. That page accepts the expected input (paste or upload), previews parsed output where applicable, and lets you copy or download the result — still client-side for the transform itself.

If you land on the wrong direction, return to /tools and search the reverse pair (for example switch from CSV to XML to XML to CSV). If you need edits mid-flight, go to /editor or a dedicated CSV/XLSX editor, then return to a converter with a cleaned file.

Common use cases

A developer searching for a YAML-to-CSV converter to flatten a config export into columns.
An analyst looking for HTML Table to CSV after copying a pricing table from a vendor page.
A GIS user finding KML to CSV or GeoJSON to CSV for placemarks and feature properties.
A bookkeeper browsing finance converters for OFX or QFX bank statement imports.
A student unsure whether they need CSV to Excel or the Online XLSX Editor for a homework handoff.
A support lead searching “sql” to decide between SQL to CSV and CSV to SQL for a ticket attachment.

How to use this tool

Open /tools and either type a format name into search or scroll to the category that matches your domain.
Confirm the card title matches your Input→Output direction (what you have now → what you need next).
Open the tool page and skim About/format notes plus common errors if the format is unfamiliar.
Paste or upload on that page, preview, and download — or switch to an editor first if the source data itself is messy.
If no single tool fits, plan a two-step path through CSV and use the directory twice.

Example

What you have / what you need

Have: API JSON export
Need: Excel attachment for a manager

Directory path to take

1) Search “json” → open JSON to CSV
2) Optional: /editor to clean columns
3) Search “excel” → open CSV to Excel
Download .xlsx for delivery

Tips for best results

Type a short format keyword (json, xml, ofx, kml) into search — results filter client-side as you type.
Read the card title as Input to Output; reversing the words means a different tool.
Open the tool page’s guide and FAQ before assuming a limitation is a bug.
Bookmark converters you use weekly; returning to a stable URL is faster than re-browsing the hub.
When no direct tool exists, convert to CSV first, then from CSV to the final format.
Use category headings to discover related tools you did not know to search for.
Prefer editors when values are wrong; prefer converters when only the file format must change.
Check blogs and format guides linked from the site when encoding or delimiter issues block a conversion.

Common errors and how to fix them

Searching for a format returns no results.: Try a shorter or more generic term — “excel” instead of a long product phrase, “bank” or “ofx” for finance files, “html” for tables and links. If the format truly is not listed, most structured data can still move through CSV as an intermediate step.
It is unclear which tool to use when both an import and export converter exist.: Pick based on the file in your hand. Import converters (JSON to CSV) start from that format and produce CSV. Export converters (CSV to JSON) start from CSV and produce that format.
A tool card seems right but the page rejects the file.: Re-read the title direction and accepted extensions. CSV to XML will not accept an .xml upload. Also confirm you did not need an editor or finance hub instead of a general data converter.
You need cleanup and conversion but only opened a converter.: Converters assume reasonably rectangular, correctly encoded input. Open /editor or the Online CSV Editor, fix headers and rows, export CSV, then return to the converter from the directory.
Two cards look almost identical in search results.: Compare the full title words in order. “HTML Table to CSV” and “HTML Table to Excel” share a source but differ in output. “HTML Links to CSV” extracts anchors, not <table> grids.
A finance or bank file is not under Data Converters.: Check Finance Tools and the finance file converter hub for OFX, QFX, QIF, IIF, and related statement formats. General JSON/XML tools are the wrong aisle for those packages.

Best practices

Bookmark specific tool pages you use most instead of starting from the directory every time.
When two tools look similar, trust the Input→Output order in the title before clicking.
Use categories for discovery and search for speed — together they cover known and unknown needs.
Read the destination page FAQ before filing a mental bug report; format quirks are usually documented there.
Prefer a two-step CSV bridge over forcing the wrong converter when a direct pair does not exist.
Keep editors and converters mentally separate: fix content in editors, change representation in converters.
Minimize sensitive columns before any conversion you might share, even though transforms run locally.

What the /tools directory is (and is not)

The tools directory is a catalog and router. It answers “which page should I open?” with search and categories. It does not paste your file into a generic engine on the hub itself.

That separation keeps each converter honest: documentation, examples, and validation match one transformation. You always know what input is expected and what output you will get.

Use the homepage or marketing pages for product overview; use /tools when you already know you need a conversion and want the shortest path to the right URL.

Categories at a glance

Spreadsheet Tools cover Excel-oriented bridges such as CSV to Excel and related table-to-workbook flows. Data Converters gather many to-CSV and from-structured-data paths (JSON, XML, YAML, SQL, HTML tables, KML, GeoJSON, and more).

File Utilities include practical extractors and text shapes such as fixed-width to CSV and HTML links to CSV. CSV Export, Developer, and Document groupings emphasize outputs aimed at code, markup, or shareable documents (Markdown, PDF, Word, QR, HTML tables, delimited variants).

Finance Tools point at bank and accounting file workflows — OFX, QFX, QIF, IIF, and the finance converter hub — separate from general developer formats on purpose.

Spreadsheet Tools — Excel and sheet-centric bridges.
Data Converters — structured data ↔ CSV family.
File Utilities — text/HTML extraction and layout helpers.
CSV Export / Developer / Document — outputs beyond plain CSV.
Finance Tools — bank and accounting file formats.

How to search effectively

Prefer short tokens: json, xml, yaml, sql, kml, geojson, excel, html, ofx, pdf, markdown. Long natural-language queries are usually worse than the format nickname.

If results are crowded, add a second token that encodes direction (“csv to” vs “to csv”) or skim titles carefully instead of opening the first card.

Search is client-side against catalog metadata. A missing result usually means a different keyword or a true gap — not a network failure of the filter box.

Import vs export: picking direction

Always start from the file you have. Holding JSON? Open JSON to CSV (or another JSON-consuming tool). Holding CSV and needing JSON? Open CSV to JSON.

People often search the destination format only (“excel”) and then pick a tool that expects Excel as input. Read the first half of the title as “what I upload.”

When you need both cleanup and a new format, direction still comes first: get to CSV (or open CSV you already have), edit, then export to the final type.

Editors vs converters

Converters transform representation: same logical rows, different serialization (JSON array, SQL inserts, Markdown table, XLSX package, and so on). They assume columns and values are mostly already correct.

Editors open a grid so you can change values, drop rows, rename headers, and apply light formatting. Use /editor, Online CSV Editor, or Online XLSX Editor when the data is wrong or messy.

A reliable heuristic: if you would do it in Excel with the mouse on cells, use an editor; if you would do it with a Save As or export script, use a converter from this directory.

Two-step paths through CSV

CSV is the interchange hub of Convert CSV. Many formats have a to-CSV tool and a from-CSV tool even when a direct A→B page does not exist.

Example: JSON to CSV, then CSV to Excel for a manager attachment. Example: HTML Table to CSV, editor cleanup, CSV to SQL for a staging load.

Two steps add a preview checkpoint — a feature, not a bug — when each hop can fail for different reasons (nesting vs delimiters vs Excel typing).

Privacy and client-side processing

Individual converter and editor pages run transforms in the browser. File contents are not uploaded to Convert CSV servers as part of those conversions. The directory page itself only helps you navigate.

Analytics and advertising on the site are separate from the transform pipeline; read the Privacy Policy for that layer. Still minimize PII in files you display on shared screens.

Because processing is local, limits are device limits: memory, CPU, and practical upload caps on editors. The catalog cannot move a 2 GB file magically just because you found the right card.

Finance, GIS, HTML, and other specialty aisles

Bank exports belong under Finance Tools / the finance file converter hub. Do not force OFX through a generic XML-to-CSV path unless you know the structure and accept a brittle result.

Map data often lands in KML or GeoJSON converters — property columns become CSV fields for analysis in sheets. HTML has two common needs: tables versus link harvests; pick the matching card.

Document outputs (PDF, Word, Markdown, QR) are for delivery and presentation after the rectangular data is trustworthy — usually after an editor pass.

Reading a tool page once you arrive

Good order: confirm the H1 matches your direction, upload or paste a small sample, read the preview, then convert the full file. Skim common errors if the preview looks wrong.

Long-form sections on each tool explain format quirks (encoding, nesting, text-safe Excel cells, SQL dialect assumptions). They exist so you do not have to rediscover footguns.

If the page is clearly the wrong aisle, bounce back to /tools rather than fighting validation — wrong tool plus “creative” file renaming rarely ends well.

Typical directory workflows

API fixture: search json → JSON to CSV → optional editor → CSV to SQL.

Vendor web table: search html → HTML Table to CSV → CSV to Excel.

Map export: search kml or geojson → to CSV → analyze in Sheets.

Statement import: open Finance Tools → OFX/QFX path → CSV for accounting.

Unknown attachment: search by extension keyword → if stuck, open /editor only after you have CSV/XLSX.

When the catalog feels overwhelming

Ignore volume. You need one card. Categories shrink the world; search shrinks it further; the title’s first format word is the final gate.

If you only ever do one job, skip the hub next time and bookmark the destination. The directory is for discovery and triage, not a mandatory home screen.

Students and mixed teams benefit from agreeing on “canonical” paths (for example always JSON→CSV→Excel) so people stop inventing one-off routes.

Related hubs and next stops

Use /editor when search results convince you the format is already CSV/XLSX and only values need work. Use format guides and blogs when failures are about encoding or delimiters rather than picking the wrong tool.

The finance converter hub is the specialist sibling of /tools for bank-oriented formats. The site FAQ and contact page are the right places for “please add format X” requests.

After you convert, keep originals until the recipient confirms. The directory will still be there; your unreproducible hand-edits might not.

Quality checklist before you commit to a tool

Confirm what file you actually have (open a few lines in a text editor if the extension lies). Confirm what the recipient needs. Confirm whether you need edits, conversion, or both.

Match Input→Output on the card. Prefer a sample conversion before a full sensitive dump. Prefer CSV intermediate when unsure.

File format identified correctly.
Title direction matches the upload you will provide.
Editor vs converter choice is intentional.
Privacy/sensitivity reviewed before preview on shared screens.
Fallback two-step CSV path identified if needed.

Frequently asked questions

How many tools are in the directory?

The directory lists the site’s converters and related utilities across spreadsheet, data, file, export, developer, document, and finance categories — spanning CSV, XLSX, JSON, XML, YAML, SQL, HTML, KML, GeoJSON, OFX, QFX, and more as the catalog grows.

Are all these tools free?

Yes. Tools listed for everyday conversions and edits are free to use with no account required. The site is supported by advertising.

Does the /tools page convert my file by itself?

No. It is a searchable catalog. Open a specific tool card to reach the page that performs that transformation in your browser.

How do I choose between JSON to CSV and CSV to JSON?

Choose based on the file you currently have. JSON to CSV starts from JSON; CSV to JSON starts from CSV. The first words of the title are the upload format.

Should I use an editor or a converter?

Use a converter when the data is already correct and only the format must change. Use /editor or a dedicated CSV/XLSX editor when you need to fix cells, headers, or rows first.

Is my data uploaded when I browse the directory?

Browsing and searching the catalog does not upload your spreadsheet. When you open a tool and convert or edit, those transforms run client-side in your browser. See the Privacy Policy for analytics and ads.

What if there is no direct converter for my formats?

Use a two-step path through CSV when possible: convert source→CSV, then CSV→destination. You can also suggest new formats via the contact page.

Where are OFX and other bank formats?

Look under Finance Tools and the finance file converter hub rather than general Data Converters. Those formats have dedicated handling.

Do the tools work on mobile?

Yes, converters and editors are responsive in mobile browsers. Large grids and heavy files are still easier on a desktop-sized screen.

Why did search miss a tool I know exists?

Try a shorter keyword (excel vs a long phrase, html vs “webpage table”). Confirm you are on /tools and that the tool is in the current catalog metadata.

Can I request a new converter?

Yes — use the contact page to suggest a format or direction. Meanwhile, approximate missing pairs with a CSV intermediate when the data is tabular.

How is /tools different from /editor?

/tools finds and opens converters (and related utilities). /editor opens a spreadsheet grid for CSV/XLSX cleanup and export. Use both in sequence when you need clean data in a new format.

For more background on data formats and conversion workflows, read our format guides or browse the converter blog for step-by-step walkthroughs linked to each tool.