No reviews yetBe the first to leave a review for CSV Viewer
Maker
📌
I'm Jean, a fullstack dev from France. This is my first launch here, so bear with me.
The backstory is pretty boring, honestly. At work, people kept sending me CSV exports. Every single time, I had to wait for Excel to open, watch it butcher my dates, turn phone numbers into scientific notation... just to check what was inside the file.
One evening I thought "this is stupid, I just want to LOOK at the thing" and started building csv-viewer.online on my free time.
What it does:
• Drag & drop a CSV, it shows up instantly
• Sort, search, filter
• No account, no install, free
What it doesn't do: it's not trying to replace Excel or Google Sheets. It's the tool you use in the 30 seconds before deciding if a file is even worth opening in a real spreadsheet.
I've been improving it slowly for a few months based on my own usage and some feedback from colleagues. Now I'd love to hear from people outside my bubble.
Be brutal, I can take it. What's missing? What's annoying? What would make you actually bookmark it?
Thanks for checking it out 🙏
Report
How does it handle really large CSVs, like millions of rows? Curious whether the local processing starts to lag or if there is a practical file size limit where it begins to struggle.
Report
Maker
@gkhan2f3a Good question. The file is parsed in streaming, 1MB chunks, and the table only renders visible rows. So the UI doesn't freeze while loading. A 50MB file takes about 2 seconds on my laptop. But yes there's a ceiling: free shows the first 100k rows and even paid I capped it at 2 million, because past that you're just fighting the browser's RAM. So millions of rows is really where the approach stops being honest. If you have a file that kills it I'd love to know the size, that's useful info for me.
Report
Loaded a messy spreadsheet and was surprised it handled odd encoding without a hiccup. The no-upload angle is genuinely useful for quick checks on work files.
Report
Maker
@hayrettinsxwdv Glad it worked! Encoding was one of my original frustrations actually. Half the CSVs I got at work were exported from old tools in Windows-1252 or ISO-8859-1 and Excel destroyed every accent. So the viewer detects the encoding before parsing (6 supported, even UTF-16 and GBK). If you find a file it gets wrong, send it my way, those are the fun bugs.
Report
How does it handle really large CSVs, like 100MB plus, does it stay fast or start to bog down in the browser?
Report
Maker
@nerminkandefer It holds up, with caveats. Parsing is done in chunks so the page never freezes, and the table only renders what's on screen so scrolling stays smooth whatever the size. 100MB is fine on a recent machine. The real limit is RAM, not the parser, since everything stays in browser memory. On an old laptop with a huge file you'll feel it. I put a hard cap at 2M rows rather than let the tab crash silently.
Report
💎 Pixel perfection
Love that everything runs locally with no upload step, the privacy angle on a tool like this is usually just a footnote but here it feels like the actual foundation. Clean execution.
How does it handle really large CSVs, like millions of rows? Curious whether the local processing starts to lag or if there is a practical file size limit where it begins to struggle.
@gkhan2f3a Good question. The file is parsed in streaming, 1MB chunks, and the table only renders visible rows. So the UI doesn't freeze while loading. A 50MB file takes about 2 seconds on my laptop. But yes there's a ceiling: free shows the first 100k rows and even paid I capped it at 2 million, because past that you're just fighting the browser's RAM. So millions of rows is really where the approach stops being honest. If you have a file that kills it I'd love to know the size, that's useful info for me.
Loaded a messy spreadsheet and was surprised it handled odd encoding without a hiccup. The no-upload angle is genuinely useful for quick checks on work files.
@hayrettinsxwdv Glad it worked! Encoding was one of my original frustrations actually. Half the CSVs I got at work were exported from old tools in Windows-1252 or ISO-8859-1 and Excel destroyed every accent. So the viewer detects the encoding before parsing (6 supported, even UTF-16 and GBK). If you find a file it gets wrong, send it my way, those are the fun bugs.
How does it handle really large CSVs, like 100MB plus, does it stay fast or start to bog down in the browser?
@nerminkandefer It holds up, with caveats. Parsing is done in chunks so the page never freezes, and the table only renders what's on screen so scrolling stays smooth whatever the size. 100MB is fine on a recent machine. The real limit is RAM, not the parser, since everything stays in browser memory. On an old laptop with a huge file you'll feel it. I put a hard cap at 2M rows rather than let the tab crash silently.
Love that everything runs locally with no upload step, the privacy angle on a tool like this is usually just a footnote but here it feels like the actual foundation. Clean execution.