pandas read_csv() — load CSV files with full control over types and parsing

What it does

read_csv() reads delimited text into a DataFrame in one call. It sniffs headers, infers dtypes per column, splits NA detection from parsing, and hands you a table — with 44 parameters to steer every step. The defaults are good; the craft is knowing which four to touch.

Why it matters

The type coercion happens the moment the file is read: '1,199.00' becomes a text column (str in pandas 3.0, object before it), a stray blank in a units column floats everything to float64, dates stay strings unless you ask. Fixing types after the fact is rework; read_csv() lets you fix them at the door — then usecols trims the file down before the parser even builds the columns.

Example

$ You received orders_q3.csv. Look at what inference did to it before you touch anything:

order_id            int64
region                str
product               str
units             float64
unit_price_eur        str
order_date            str
dtype: object

$ Right-size the dtypes so the DataFrame matches reality — IDs as int32, counts as float32:

order_id            int32
region                str
product               str
units             float32
unit_price_eur        str
order_date            str
dtype: object

$ European exports use thousands separators, and you only need four columns with real dates. Strip, parse, trim — in one call:

   order_id region  unit_price_eur order_date
0      1001  North         1199.00 2026-07-14
1      1002  South          229.90 2026-07-15
2      1003   East         1199.00 2026-07-18
3      1004   West           89.50 2026-07-21
4      1005  North         229.90 2026-08-02
5      1006   East          59.99 2026-08-09
6      1007  South         1199.00 2026-08-27
7      1008   West          229.90 2026-09-05

datetime64[us]

$ The file is 40 GB and your RAM is not. Stream it in chunks and accumulate:

13981.45

Common flags

sep / delimiter

Field separator. The C engine takes single characters; sep=None is handled by the Python engine, which sniffs the delimiter from the first valid row with csv.Sniffer, and a regex or multi-character separator forces that same engine. delimiter is a plain alias for sep.

usecols

Read only named columns — saves parse time and memory before the DataFrame exists.

dtype

Dict of {column: type}; wins over inference, ideal for int32 IDs or string columns that inference would mangle.

parse_dates / date_format

Columns to parse as dates; pair with date_format to nail non-ISO layouts.

converters

Dict of {column: function} applied per cell — the escape hatch when no parameter can clean the value.

na_values / keep_default_na

Extra strings to treat as missing; keep_default_na=False stops 'NA' (Namibia) becoming NaN.

na_filter / chunksize

na_filter=False skips NA scanning on clean files; chunksize=N streams big files as an iterator of DataFrames.

engine='c' | 'python'

The C engine is the default and engine='python' is the fallback — the only one that supports skipfooter, and on pandas 3.0.3 asking the C engine for skipfooter does not raise, it prints 'Falling back to the python engine because the c engine does not support skipfooter'. Measured here on a 200k-row, 5.6 MB CSV: the C engine read all four columns in 0.112 s; usecols=['a','b'] cut that to 0.051 s and the frame from 16.7 MB to 3.2 MB.