Data & Spreadsheets

TableConvert

Convert tabular data between formats such as Markdown, CSV, JSON and spreadsheet-friendly representations.

Visit website
Free optionOfficial source checked Task notes available ↓
A limit worth knowing

Edit a CSV without losing IDs

Read the failure notes before using its CSV-to-CSV route for quoted fields.

Keep in mind

All four primary saved files failed the full-table check in version 3.0.1. Use a route that passes your sample first.

See the steps, results & sample files

What you can use it for

  • table conversion
  • markdown tables
  • json conversion
A practical starting point

Check quoted fields before trusting a CSV export

Evaluate the exact conversion route with a sample before using it on important records.

TableConvert 3.0.1 CSV-to-CSV test on 10 October 2026 failed the quoted-field sample. Other routes and later versions were not tested.

A short workflow

  1. Use a copy containing quoted commas and quotes as well as long identifiers.
  2. Export without making edits first; check that each row still has the expected number of fields.
  3. Stop if strict parsing or a reopen changes the data. Our recorded route failed this check; keep the original.
TableConvert reopened synthetic CSV showing quoted text split or truncated into cells.
Historical failed-route screenshot, 10 October 2026. See the downloadable exports for the full parsing result. View full size ↗

Before you start

Were the leading-zero fields enough to make the export usable?

No. Those identifiers survived a tolerant diagnostic parse, but malformed quoting made the complete CSV invalid.

Does this mean every TableConvert feature fails?

No. The finding is limited to the dated CSV-to-CSV route and sample described in the evidence.

Notes based on evidence checked .

Before you choose

General feature limits remain unverified; see the task-specific test below.

Edit CSV without changing identifiers

On 10 October 2026, TableConvert 3.0.1 completed opening, editing, saving and reopening our 7-row CSV, but all 4 primary saved files failed strict CSV/value checks. In both UTF-8 input variants, a quoted comma split r01.note into two cells; output gained a seventh column and malformed embedded quotes. The text IDs remained unchanged in diagnostic parsing. This is a task-specific failure in CSV-to-CSV mode, not a test of every converter.

This check covers one small synthetic table and the specified CSV editing route. It does not verify every product feature, large-file performance or recovery of values already changed elsewhere.

Edit CSV: Keep Leading Zeros and Long IDs — settings, exact field checks, actual exports and alternatives.

Task verification and evidence

Third-party CSV editing tests with one synthetic table. Tested 10 October 2026. ConvertCSV passed this sample; TableConvert 3.0.1 failed the tested CSV-to-CSV route. Original failed exports are preserved.

These checks apply to the stated inputs and route. General pricing, platform and processing fields keep their own source dates and unknown values.

Evidence files and checksums — csv-preservation-v1

About this listing

Website checked
Official sources reviewed on . These general listing fields are based on public product information. The task-specific test above has its own scope and limits; it does not verify all product features.

Features and plans change. If something here is out of date, suggest a correction.

Choose by the job

Other routes worth considering

Alternatives and useful next steps, with their limits made clear.

Alternative for this task

ConvertCSV

For this specific CSV editing task, ConvertCSV preserved the same seven-row sample in all four saved-file checks. Recheck your own data.

See details & evidence ↗
Curated collections

See how it fits the task.

Shortlists with a reason for every choice.

All collections ↗

More in this category

See all ↗

Estimate a spending allowance before giving an AI agent access to paid services. Enter expected tasks, unit cost and a buffer to generate daily, monthly and per-payment budgets plus a JSON configuration outline.

  • Agent cost planning
  • API spend budgets

Use TradingView analytical scripts to organise manual chart review, market structure, scenario planning and portfolio context.

  • Structure chart-analysis workflows
  • Review risk scenarios