Data cleaning for analysts who've outgrown Excel

Clean 10M-row files right in your browser.

Mungr runs DuckDB, a real analytical database compiled to WebAssembly, inside your browser. Clean millions of rows of CSV without uploading a byte, installing anything, or waiting on IT.

Try it now, no sign-up →

No sign-up to try · Guest files up to 50MB · Free account up to 5GB · Your data never leaves your browser

100% client-side
DuckDB + WASM
Tested at 10M+ rows
Built for HIPAA & GDPR
messy_export.csv · 9.8 GB on disk cleaning…
A
B
C
D
1
J.DOE@MAIL..COM
13/45/2024
 1,204  
NULL
2
m.tan@corp.io
2024-02-02
88
active
3
m.tan@corp.io
2024-02-02
88
active
4
Müller, A.
2024-02-09
312
active
0 rows processed · 0 bytes uploaded
The usual options

If you work with regulated data, none of the usual tools actually work for you.

Every option fails a different way. In healthcare, finance, or legal, that failure can be a compliance violation.

OptionBreaks aroundWhat happens
Excel / Google Sheets Heavy formulas & large files It slows to a crawl long before you reach the row limit, especially with real formatting and formulas.
OpenRefine / local scripts >1M rows It needs installing and IT sign-off before anyone can touch it. Then it runs out of memory the first time someone hands it a real export.
Cloud data platforms No row limit They handle the scale, but at real cost. And you still have to upload raw data off your device to get there.
Healthcare, finance & legal teams Every file Uploading data anywhere, cloud tool or not, risks a HIPAA, GDPR, or client-confidentiality violation before you've cleaned a single row.

What if cleaning your data never required uploading it in the first place?

The fix

A real query engine that runs in your browser and never uploads your file.

Under the hood it is DuckDB, the same engine analysts run on a server.

Handle 10M+ rows without the spinning wheel

DuckDB compiled to WebAssembly runs a full analytical engine inside the page, so parsing and querying happen at database speed instead of JavaScript CSV speed.

Tested at 10M+ rows on 16GB RAM laptops (Lenovo & Dell) with no crash

Your data never leaves your device, PII included

Processing happens entirely client-side. Smart Scan flags PII against known categories like HIPAA Safe Harbor so you can mask, redact, or hash it before it is shared.

No upload means no HIPAA or GDPR exposure

Zero install, zero setup

It's a web app. Open a tab, drop a file, and start cleaning. No pip installs, no Docker, no IT ticket.

Time to first cleaned row: under 30 seconds
Data munging · data wrangling · data cleansing

What's the difference between data munging, data wrangling, and data cleansing?

They all describe the same job: getting raw, messy data ready for analysis. The terms overlap, but each leans a little differently, and Mungr covers all three.

Data munging

Munge it into shape

Data munging means transforming raw data into a usable format: fixing date formats, mapping aliases, combining fields, and resolving inconsistencies. It's the "get this mess into a shape I can work with" step of data preparation.

Data wrangling

Wrangle it into order

Data wrangling covers the whole loop: discovering problems, cleaning them, restructuring, and validating the result. Many analytics teams use "data wrangling" as the umbrella term for all of data preparation.

Data cleansing

Clean out the errors

Data cleansing is the cleaning part specifically: removing or fixing incorrect, duplicate, incomplete, or wrongly formatted records. Think null handling, deduplication, and standardizing values before analysis.

Whether you call it data munging, data wrangling, or data cleansing, Mungr does all three in your browser with zero uploads. It's the data cleaning tool for analysts who refuse to send sensitive files to a server. Read the data cleaning 101 guide, see how Mungr stacks up against other data cleaning tools, or read the docs.

Compliance that comes from the architecture

Mungr finds the PII. You decide what happens to it.

Nothing leaves your browser, so HIPAA and GDPR stop being a separate cleanup step. The exposure never happens in the first place.

facilities.csv Cleaned Smart Scan
phoneVARCHAR
facility_typeVARCHAR
bed_countBIGINT
accreditedBOOLEAN
phoneVARCHAR
⚠ Sensitive PII detected

Phone number (HIPAA Safe Harbor #5). Mask or redact before sharing externally.

Mask Redact Hash
Null values0 (0%)
Unique values25
Total values25
Smart Scan Results Found 2 issues across 10 columns in 558ms
1 compliance
phone: Phone detected (HIPAA Safe Harbor #5)

25 of 25 rows (100%) match phone pattern. Consider masking before sharing. 25 rows

1 integrity
bed_count: High null rate (68%)

17 of 25 values are missing. Consider filling with a default or filtering these rows. 17 rows

Dismiss Apply Selected
Clean once, reuse forever

Turn your cleaning steps into a recipe your whole team can reuse.

Build the sequence of steps once, save it as a recipe, and export it as JSON. Next time the same kind of export lands on your desk, a clean file is one click away.

1 Trim whitespace on all columns
2 Standardize case on email
3 Standardize date format on admitted_date
4 Mask PII in phone HIPAA Safe Harbor
5 Fill nulls in bed_count with 0
6 Extract with regex from zip_code
+ 9 more steps…
recipe_facilities_cleanup.jsonCopy JSON
{
  "recipe": "facilities_cleanup",
  "steps": [
    { "op": "trim", "cols": "*" },
    { "op": "case_standardize", "col": "email" },
    { "op": "date_standardize", "col": "admitted_date" },
    { "op": "pii_mask", "col": "phone", "rule": "hipaa_safe_harbor" },
    { "op": "fill_null", "col": "bed_count", "value": 0 }
  ]
}

Share the JSON in Slack, Notion, or your team's recipe library. Anyone on the team can load it and apply the same clean-up to their own file, and nothing about the underlying data has to be shared for the recipe to work.

10M+
rows cleaned and tested, no crash
0
bytes of your data ever sent to a server
50MB
free per file with no sign-up, 5GB with a free account
Pricing

Try it free. No sign-up to start.

Clean files up to 50MB right away. A free account adds 5GB of processing, saved recipes, and larger files.

Monthly Yearly save ~20%
  Guest Free Propopular Team
Price $0 $0 $29/mo $23/mo $49/mo per seat $39/mo per seat
Sign-up None, start cleaning Free account Account + subscription Account + subscription
Max file size 50 MB 100 MB 1 GB Unlimited
Processing Session only, nothing stored Up to 5 GB total Unlimited Unlimited, pooled across seats
Transforms 15 core steps All 19 steps All 19 steps All 19 steps
Saved recipes None (session only) 3 recipes Unlimited Unlimited + shared library
Recipe history None Last 3 recipes Version history Version history
Data location Never leaves your device Never leaves your device Never leaves your device Never leaves your device
Collaboration None None Saved pipelines Shared recipe library & admin roles
Open workspace Register Free Get Pro Get Team

Need more room without a subscription? Buy a one-time top-up of 5GB for $5 ▸ , no expiry rush, usable whenever you need it.

Student, academic, or nonprofit? Apply for a discount ▸

Need a fairer price where you live? Ask about Purchasing Power Parity (PPP) pricing at hello@getmungr.com

Under the hood

Built for real-world messy data.

Every feature exists because a real file broke a real tool first.

01

Native CSV & Parquet

Read columnar Parquet files directly at columnar speed, with no conversion step needed.

02

19 data cleaning operations

Standardize dates and casing, trim whitespace, handle nulls, deduplicate, and extract fields with presets or your own regex.

03

Automatic PII detection & redaction

Flags identifiers against known compliance categories like HIPAA Safe Harbor, then masks, redacts, or hashes them in one click.

04

Smart Scan

One click surfaces compliance and data-integrity issues across every column, with a recommended fix for each.

05

Streaming architecture

Processes data in chunks instead of all at once, so a 10M-row file doesn't need 10M rows of RAM.

06

Recipes you can share

Save your cleaning steps, export them as JSON, and let your team apply the exact same clean-up to the next file in one click.

07

Works offline

Once it loads, no connection is required to keep cleaning. Your data was never going anywhere anyway.

Before you ask

The questions every data analyst and data engineer asks us

We'd rather answer these now than have you wonder later.

No. Open the workspace and clean files up to 50 MB per file with no account at all. Create a free account when you want to save recipes, clean files up to 100 MB, and use your 5 GB of total processing, or upgrade for 1 GB files and unlimited usage.
We don't process, see, or store your data. It never leaves your browser, so there's nothing for us to monetize even if we wanted to. The free tiers are subsidized by Pro and Team plans for people who need more headroom and collaboration.
Yes, that's the whole point. DuckDB-WASM uses columnar, streaming execution, so memory use stays roughly flat even as row count climbs. We've tested it at 10M+ rows on standard 16GB RAM laptops (Lenovo and Dell) without a crash.
You'll get a clear warning before you hit it, with an option to upgrade. We never silently fail or corrupt your work mid-clean.
Open your browser's dev tools, go to the Network tab, and load a file. You'll see zero outbound requests carrying your data, because there's nowhere for it to go.
Yes. Mixed UTF-8/Latin-1 encodings, ragged rows, stray delimiters, and nested Parquet schemas are exactly the cases Mungr was built to handle.
Compliance here follows from the architecture, so you do not have to take it on trust. Your file is never uploaded, which means no transfer to log, no BAA with a vendor, and no server-side breach surface. Smart Scan also flags identifiers like phone numbers and SSNs against HIPAA Safe Harbor categories, so you can mask or redact them before sharing a cleaned export.
When you load a file, Smart Scan checks each column against known PII patterns (phone numbers, SSNs, emails, and more) and tells you exactly which HIPAA Safe Harbor category it matches, with links to the relevant guidance. From there you choose to mask, redact, or hash. Nothing happens automatically without your say.
Yes. Any sequence of steps can be saved as a recipe and exported as JSON. Share it however your team already shares things (Slack, Notion, a shared drive), and anyone can load it and apply the exact same clean-up to a similar file in one click. The recipe travels. The data never has to.
Yes. Data munging, data wrangling, and data cleansing all describe the same job: turning raw, messy data into something ready for analysis. Mungr is exactly that, and it does it in your browser with zero uploads, which most data munging tools can't claim.
Data munging means transforming raw data into a usable format. Data wrangling is the broader loop of discovering, cleaning, restructuring, and validating data. Data cleansing focuses on fixing incorrect, duplicate, or missing records. They overlap heavily, and Mungr covers all three with transforms for dates, casing, nulls, duplicates, PII, and more.
No relation. Mungr (spelled M-U-N-G-R) is a data cleaning and data munging tool for analysts and data engineers. We clean data, not portfolios. The name comes from combining "mung" and "r", not from any person.

Stop fighting your file size.
Start cleaning.

No sign-up to try. Free account up to 5GB. No install. No upload. No credit card.

Try it now, no sign-up →

Set up in under 60 seconds · Your data stays on your device, always

Clean 10M rows, privately.

Try free, no sign-up