Skip to content
DEDataEngUtils

Merge CSVs → Parquet

Combine multiple CSV extracts into one Parquet dataset in your browser — ideal when logs, exports or shard files land separately but need to load as a single table. DataEngUtils merges locally with an Apache Arrow engine compiled to WebAssembly, so you never concatenate sensitive rows in an external uploader. Align schemas, drop duplicate headers and emit one compact Parquet file ready for DuckDB, Spark or warehouse COPY commands. It is tuned for data engineers who receive weekly vendor dumps and want a repeatable merge step before validation, all without leaving the browser.

Open it in the app

Merge CSVs → Parquet runs in the DataEngUtils browser app on a Rust engine (Apache Arrow) compiled to WebAssembly — part of the Pro workbench, entirely client-side, and nothing is uploaded.

app.dataengutils.com
Merge CSVs → Parquet in the DataEngUtils app

How it works

  1. 1. Open Merge CSVs → Parquet

    Open the tool in the DataEngUtils app — nothing is uploaded.

  2. 2. Add the CSV files to merge

    Select two or more CSV files. Order matters when timestamps or partitions are involved.

  3. 3. Merge and download

    Harmonize column mismatches, then write a single compressed .parquet file.

Why not use an online tool?

Online converters tools require uploading your Parquet and CSV files to a third-party server. For production work, that is a security and compliance risk. DataEngUtils runs a client-side engine in your browser — same convenience, none of the exposure.

Frequently asked questions

What if the CSV schemas differ?
The tool surfaces column mismatches so you can fix types or exclude fields before merging.
Does merging upload my files?
No. Parsing and merging happen locally in your browser with a WebAssembly engine.
Can I merge into CSV instead?
This tool optimizes for Parquet output. Use Parquet → CSV afterwards if you need CSV.