How to Open Pipe-Delimited (PSV) Files

If you have ever opened a file full of vertical bars and wondered what tool could make sense of it, this guide is for you. Pipe-delimited files are everywhere in data exports and system feeds, yet they look like gibberish in the wrong viewer. Here is what a PSV file actually is, why it confuses ordinary editors, and how to open, view, edit, and convert one without scrambling a single field.

What a pipe-delimited (PSV) file is

A pipe-delimited file is a plain-text table where the vertical bar character — |, the pipe — separates one field from the next. It is the same idea as a CSV, except the separator is a pipe instead of a comma. These files usually carry a .psv extension, and "PSV" stands for pipe-separated values.

A single row looks like this:

1001|Smith, John|Phoenix|AZ

A parser that splits on the pipe reads four fields: 1001, Smith, John, Phoenix, and AZ. The pipe is the only character doing the splitting. Notice the comma inside Smith, John — in this format it is just ordinary data, because the pipe, not the comma, marks the field boundaries. That is the whole point of the format.

Why people use pipes instead of commas

The pipe earns its place for one simple reason: it almost never shows up inside real data. Names, addresses, prices, and free-text comments are full of commas. They contain tabs less often, but still sometimes. A vertical bar, though, rarely appears in everyday values, which makes it a safe separator.

That safety matters most when the data itself is messy:

• Data full of commas. Addresses (123 Main St, Suite 4), full names (Smith, John), and currency (1,000.50) all contain commas. In a comma CSV every one of those fields has to be wrapped in quotes to survive. Switch to a pipe and the quoting mostly disappears, because the data has no pipes to collide with.
• Database dumps. Many database export tools default to pipe delimiters precisely so they do not have to quote every comma-laden text column.
• Log files and feeds. System logs and data pipelines often pipe-delimit their records so downstream tools can split on a character that will never appear inside a message.

In short, pipes win when commas and tabs are both unreliable. If you want the fuller picture of how all four common separators compare, see CSV delimiters explained.

Why a PSV file looks like one jammed column

Open a pipe-delimited file in a tool that assumes commas, and you get a wall of text that all sits in a single column:

1001|Smith, John|Phoenix|AZ
1002|Doe, Jane|Tucson|AZ

Nothing is broken here — the tool simply split on the wrong character. It scanned each line looking for commas to break on. In a clean pipe-delimited file there are no separating commas at all, so the tool finds nothing to split on and treats the entire line as one field. The result is one tall, useless column of raw text with visible bars running down it.

This is the same confusion that makes semicolon files look garbled in comma-expecting tools. The fix is identical: parse the file on the character it actually uses. Once a viewer splits on the pipe, those same two lines snap into four tidy columns.

How to open and view a PSV file

The reliable way to open a pipe-delimited file is to use an editor that detects the delimiter for you, so you never have to configure anything by hand.

1. Open the file. Drag your .psv (or any pipe-delimited .txt) onto CEESVEE, or use File then Open. You can also right-click the file and use "Open with" if you have set up the file association.
2. Let auto-detection do its job. CEESVEE scans the first rows and picks the separator that produces the most consistent column count across lines. For a real pipe-delimited file, splitting on the pipe lines up every row, so it wins. The encoding (UTF-8, UTF-16 LE/BE, or Windows-1252) is detected the same way, and the byte-order mark is handled correctly.
3. Confirm the columns look right. Glance at the grid. Every value should sit in the column you expect, with no field obviously split or merged. The pipes are gone, replaced by clean column borders.
4. Override the delimiter if needed. If detection ever guesses wrong — an unusual file, or one with very few rows — open the delimiter setting and choose pipe manually. There is also a custom-delimiter option for anything exotic. The grid re-parses instantly so you can verify the result.

Because the grid is virtualized and backed by a Rust core, this works just as smoothly on a small lookup table as on a database dump with a million rows and 100 MB or more — the file opens fast and scrolls without lag.

Editing a pipe-delimited file

Once the file is a proper grid, you edit it like any spreadsheet. Click a cell to change its value, sort by one or more columns to group records, and use find and replace — plain text or regex — to clean up values in bulk. A frozen header keeps your column names visible as you scroll, and live stats give you a quick read on row and column counts. Tabs let you keep several delimited files open at once.

The key thing is that you are editing data, not raw text. You never have to count pipes or worry about lining up bars by hand. The editor tracks the real field boundaries for you.

Converting a PSV to a comma CSV (or back)

Sometimes a downstream tool insists on a comma CSV, and you need to convert the pipe-delimited file. This is where editing data rather than text pays off, because a blind find-and-replace of pipes to commas would be unsafe the moment a field contains a comma. The correct method is to let the editor parse and re-serialize the file.

1. Open the .psv so the columns are correctly parsed in the grid.
2. Choose Save As to bring up the export options instead of overwriting in place.
3. Set the delimiter to comma. This is the one setting that performs the conversion.
4. Adjust the other output options if needed. The same dialog exposes encoding, quoting style, line endings (LF or CRLF), and whether to write a BOM. Leave them for a clean round-trip, or tune them if the destination is picky.
5. Name the file with a .csv extension and save. CEESVEE re-serializes every field, automatically quoting any value that now contains a comma, so Smith, John stays a single field instead of splitting into two.

The reverse works the same way: open a comma CSV, Save As, set the delimiter to pipe, and save as .psv. For a deeper walkthrough of converting between separators safely, see how to change a CSV delimiter. If you are dealing with the related semicolon problem, opening semicolon CSV files covers that case.

The bottom line

A pipe-delimited (PSV) file is just a table that uses the vertical bar to separate fields, chosen because pipes almost never appear inside real data. It looks like one jammed column only because comma-expecting tools split on the wrong character. Open it in a viewer that detects the pipe, and the columns fall into place — no manual setup, no scrambled rows.

Download CEESVEE for free to open, edit, and convert pipe-delimited files with the delimiter detected for you. It is fast, 100% local, and open source under the MIT license — you can read the code on GitHub.