How to Parse CSV in Node.js (Streaming and Sync)

Why Streaming Beats readFileSync

Small CSVs are easy—read the whole file and parse once. Real workloads are not always small. Streaming lets Node.js process CSVs that would otherwise exhaust memory, and it keeps the event loop free for other tasks.

Choose sync for scripts under a few megabytes. Choose streaming for anything you might run in a server or long-running job.

Pick a Library

All three are solid. Pick based on how the rest of your stack looks.

Step-by-Step: Streaming with csv-parse

The canonical streaming pattern in Node.js.

import fs from "node:fs";
import { parse } from "csv-parse";

const parser = parse({
  columns: true,
  skip_empty_lines: true,
  bom: true,
});

fs.createReadStream("orders.csv")
  .pipe(parser)
  .on("data", (row) => {
    // process one row
  })
  .on("end", () => console.log("done"))
  .on("error", (err) => console.error(err));

import fs from "node:fs";
import { parse } from "csv-parse/sync";

const text = fs.readFileSync("small.csv", "utf8");
const rows = parse(text, { columns: true, skip_empty_lines: true, bom: true });
console.log(rows[0]);

import { pipeline } from "node:stream/promises";
import { Transform } from "node:stream";

await pipeline(
  fs.createReadStream("orders.csv"),
  parse({ columns: true, bom: true }),
  new Transform({
    objectMode: true,
    transform(row, _enc, cb) {
      if (row.status === "paid") this.push(row);
      cb();
    },
  }),
  async function* (source) {
    for await (const row of source) yield JSON.stringify(row) + "\n";
  },
  fs.createWriteStream("paid.ndjson"),
);

Writing CSV in Node.js

csv-stringify is the mirror of csv-parse.

import fs from "node:fs";
import { stringify } from "csv-stringify";

const stringifier = stringify({ header: true });
stringifier.pipe(fs.createWriteStream("out.csv"));
stringifier.write({ id: 1, email: "ada@example.com" });
stringifier.write({ id: 2, email: "grace@example.com" });
stringifier.end();

Encoding, BOM, and Delimiters

Same rules as everywhere else, but easy to forget in a server.

Real-World Examples

Common shapes of Node.js CSV work.

Common Mistakes

Avoid these to keep production stable.

• readFileSync on huge files, running out of memory.
• Not enabling bom, so "\uFEFForder_id" appears as a header key.
• Assuming every row has every column.
• Blocking the event loop with sync parsing in a server.
• Missing error handlers on streams.

Best Practices

A little discipline scales.

• Prefer streaming for anything user-triggered or scheduled.
• Handle errors with .on("error") and pipeline().
• Enable bom for CSVs that may come from Excel.
• Log row counts before and after transforms.
• Validate required columns early and bail with a clear message.

Why Use Convert CSV Online?

Sometimes the fastest debug is a browser preview. Convert CSV Online is free, browser-based, and needs no account for everyday conversions. Preview the CSV in the Online CSV Editor before wiring up your Node.js pipeline. Client-side workflows run on Windows, macOS, and Linux browsers.

Conclusion

Node.js parses CSV well with the right library and streaming pattern. Choose csv-parse or fast-csv, handle errors, and enable BOM support for files from Excel.