How to Select Specific Columns From a CSV Without Writing SQL

The SQL way to select specific columns from a table is a SELECT statement: SELECT name, email, phone FROM contacts. It is clean, fast, and precise — if you have a database and know SQL.

But if you have a CSV file sitting on your desktop and you do not want to spin up a database just to extract a few columns from it, there is a faster path: a free browser column editor that does the same thing visually, in seconds, with no code and no database required.

The SQL SELECT Approach and Its Requirements

To use SQL to select columns from a CSV, you need:

• A database system (SQLite, PostgreSQL, MySQL, etc.) installed and running
• The CSV imported into a table in that database
• Knowledge of SQL syntax
• A way to export the result back to CSV

For people who work with databases regularly, this is fast. For everyone else, it is substantial overhead for what is ultimately a simple structural change to a file.

The No-Code Alternative

1. Open the free column editor in your browser.
2. Upload your CSV (or XLSX, TSV, ODS, XLS).
3. All column names appear as a checklist.
4. Uncheck every column you do not need — or uncheck all, then check only the ones you want to keep.
5. Click Download.

The result is a CSV containing only the columns you selected, in the order they appeared in the original file (or a reordered sequence if you used the arrows). Equivalent to: SELECT col_a, col_b, col_c FROM your_csv.

Sell Custom Apparel — We Handle Printing & Free Shipping

Reordering the Selected Columns

In SQL, the order of columns in a SELECT statement determines the column order in the output:

SELECT email, name, phone FROM contacts

puts email first, name second, phone third — regardless of their order in the table.

The column editor's arrows do the same thing visually. After selecting which columns to keep, use the up/down arrows to place them in whatever order the output needs. This matches the behavior of a SQL SELECT with a specific column sequence.

When SQL Is Still the Right Tool

A browser column editor is better for one-off column selection on individual files. SQL is better when:

• You need to filter rows as well (WHERE clauses)
• You need to join data from multiple files or tables
• You are automating the same extraction repeatedly on new files
• The file is very large (hundreds of MB) and browser memory becomes a constraint
• You are already in a database environment

For purely structural column selection on a single file, the browser tool is faster every time.

SQLite as a Middle Ground

If you find yourself needing SQL-like column selection frequently, SQLite is worth knowing. It is a lightweight database that runs as a single file — no server required. Tools like DB Browser for SQLite let you import a CSV, run a SELECT query, and export the result — all without setting up a full database server. It is more powerful than a browser tool but far less overhead than a full RDBMS.

Frequently Asked Questions

Can I select columns from a CSV using Excel instead?

Yes. In Excel, you can hide or delete unwanted columns and save as CSV. But for many columns, the browser tool is faster — a visual checklist is quicker than selecting and deleting multiple columns in Excel.

What is the command-line equivalent of this for CSV files?

On Unix/Mac, the cut command can select specific fields from a CSV: cut -d"," -f1,3,5 file.csv. csvkit's csvcut tool is more robust for complex CSVs. These are good options if you are comfortable in the terminal.

Can I save the column selection to reuse on future files?

The browser tool does not save session state. For a repeatable selection pattern applied to many files, a short Python script or a csvcut command in a shell script would be more efficient.

Is this free?

Yes. No account, no database, no cost.