How to use Fixed-Width File to CSV Parser
- Paste fixed-width text and review the sample lines.
- Toggle numbered column boundaries, guess from spacing or edit the column plan.
- Write the plan from the ruler when using its controls, then check positions and widths.
- Convert the text, inspect unmapped-character notes and download the CSV.
Example: Fixed-Width File to CSV Parser
Extract identifiers, names and quantities.
Options
- Fixed-width text
- Up to 20 MB of UTF-8 text and 100,000 lines. Positions count Unicode code points, not bytes.
- Column plan
- One column per line as name | start | width. Start positions are 1-based and columns must not overlap. Up to 500 columns.
- Trim each cell
- Removes leading and trailing spaces inside each column, which is usual for padded fixed-width data. Turn it off to keep the padding.
- Blank lines
- A blank line never receives a value. Keeping it writes a row of empty cells so line numbers stay aligned; dropping it removes the row.
- Output delimiter
- Choose comma, semicolon, tab or pipe for the exported table. This setting does not locate input fields; the column plan's specified positions and widths do that.
- Protect spreadsheet formulas
- The fixed-width slicing CSV export can prefix formula-like source text, including after leading whitespace. This changes the stored text; review the downloaded cells before using them.
Supported inputs and limits
- Up to 20 MiB of UTF-8 text, 100,000 lines and 500 planned columns.
- The column plan is limited to 20,000 characters, with names up to 60 characters.
- Positions are one-based Unicode code points, not bytes or grapheme clusters.
- Ranges must not overlap, and short nonblank records are refused.
- Ruler controls and spacing guesses are aids to a plan you must review.
More details
Unmapped text is reported and excluded from CSV.
Formula protection can prefix exported values.
Where your input is processed
This tool does not upload your inputs. See the limits for anything saved on your device.
A fixed-width layout needs the source specification
A visible gap does not prove a field boundary. Use the actual start and width for each field, especially when values contain spaces. Overlapping or invalid specifications are refused. The output keeps values as text, so identifiers with leading zeroes remain identifiers.
Character positions can differ from byte positions
The tool slices decoded text by the supported character convention. A multibyte encoded source described by byte offsets can have different boundaries. Decode the file deliberately and test a record containing non-ASCII characters before relying on a legacy byte-based layout.
Questions about Fixed-Width File to CSV Parser
Do column positions refer to bytes?
No. They refer to Unicode code points. A multibyte character still occupies one code-point position, while a combining sequence can occupy several.
What happens when a record is too short?
A nonblank record that cannot cover the selected ranges is refused with its line number. Check the specification or source record.
Can I leave gaps between columns?
Yes, provided ranges do not overlap. Unmapped content is reported for review instead of being presented as extracted data.