Is the input column-aligned, delimiter-based, log-shaped, or table markup?
Use fixed-width parsing for aligned records, messy-text tooling for inconsistent delimiters, log tools for event lines, and Markdown or HTML extraction for embedded tables.
Elysia Tools
Navigation
Workflow Playbook
Parse fixed-width records, messy delimited text, logs, Markdown tables, and HTML tables into CSV, JSON, XML, or Excel with reviewable cleanup steps.
New to this workflow? Follow the steps in order, starting with the first tool below. Already know what you need? Jump straight to the matching step — every tool in this workflow is listed in the comparison table.
First tool: Fixed-Width Column Parser
Hubs
| Tool | What it does | Category |
|---|---|---|
| Fixed-Width Column Parser | Parse fixed-width text with explicit or inferred field boundaries, character or UTF-8 byte positions, schemas, and anomaly reports. | Text Processing |
| Messy Text to Structured Data Workbench | Infer tables from pasted text, mixed delimiters, key-value lines, or HTML and export CSV, JSON, and Markdown. | Text Processing |
| Structured Log Analyzer | Detect common log formats, extract core fields, infer field types, and export parsed logs as JSON, CSV, or SQL inserts | Data Processing |
| Text Pipeline Builder | Run a portable text-cleaning recipe and inspect every step, diff, timing, and character change. | Text Processing |
Hubs
| Text to CSV Converter | Convert various text formats to CSV with customizable parsing options | Text Processing |
| Text to JSON Converter | Convert various text formats to JSON with customizable parsing options | Format Conversion |
| Text to XML Converter | Convert various text formats to XML with customizable structure and formatting options | Format Conversion |
| Text to Excel Converter | Paste CSV, TSV, JSON, key-value, or INI text and download a formatted XLSX spreadsheet | Format Conversion |
| Markdown to CSV | Convert Markdown table data to CSV format | Format Conversion |
| HTML Table to CSV | Extract and convert HTML table data to CSV format | Format Conversion |
| Log Parser - Apache/Nginx Access Log Parser | Parse Apache/Nginx access logs using regex patterns and extract structured data | Data Processing |
| Logfmt to JSON Structured Log Bridge | Convert logfmt (key=value) to JSON or JSON back to logfmt, with quote escaping, number/boolean coercion, and duplicate-key handling. | Format Conversion |
| CSV Malformed Row Surgeon | Surgically repair malformed CSV rows one at a time: unescaped (stray) quotes, mixed delimiters (tab/semicolon/comma in the same file), BOM-prefixed headers, CRLF/CR line endings and trailing empty lines. The surgeon parses tolerantly, shows a row-level red/green diff of every change it made (before → after, with the repair reason tagged), lists the rows it accepted unchanged, and emits the cleaned CSV. Optional AI repair can review suspicious rows after the deterministic pass. It complements the CSV Validator (which only reports problems) by actually fixing the damaged rows. | Development |
Semi-structured extraction fails when every input is treated as plain CSV. A fixed-width report, a mixed-delimiter support export, a Markdown table, and a logfmt trace each need a different first move. Use fixed-width-column-parser, messy-text-to-structured-data-workbench, or structured-log-analyzer to classify the source and preserve a few representative rows before changing anything.
The safest workflow separates cleanup from conversion. Use text-pipeline-builder to trim whitespace, remove repeated headers, standardize separators, and make the transformations repeatable. This prevents a one-off manual fix from hiding the exact rule that changed the data.
Once the text is stable, choose the export format deliberately. text-to-csv and text-to-excel are best for analysts, text-to-json is useful for APIs or fixtures, and text-to-xml fits schema-oriented exchange. For existing tables, use markdown-to-csv or html-table-to-csv so cell boundaries are preserved instead of re-parsed from raw text.
Logs and malformed rows need their own review pass. Use log-parser, logfmt-to-json-structured-log-bridge, and structured-log-analyzer to keep event fields consistent, then run csv-malformed-row-surgeon when row lengths or quoting issues would break an import. A complete handoff includes the parser assumptions, row counts, repaired records, and known exceptions.
Workflow playbook
Identify whether the evidence is fixed-width text, inconsistent delimited records, pasted tables, or log lines, then keep a small failing sample for validation.
Build a repeatable cleanup pipeline for trimming, splitting, replacing noise, and stabilizing separators before records are exported.
Export normalized text or extracted Markdown and HTML tables into the target interchange format while preserving headers and cell boundaries.
Handle application, web, and logfmt records separately, then repair malformed CSV rows and recheck the final table before delivery.
Use fixed-width parsing for aligned records, messy-text tooling for inconsistent delimiters, log tools for event lines, and Markdown or HTML extraction for embedded tables.
Normalize first when whitespace, quoting, mixed separators, repeated headers, or broken rows could shift columns during conversion.