CSV, JSON, regex, binary blobs and source verification - the day-job tools of working with data.
The tools that come up when the actual job is interpreting data rather than collecting it: CSV viewer with column typing for the export you just got from the database, JSON formatter for the API response, regex tester against the source string, base64 for the binary blob someone embedded in a JSON field, hash for source verification, and the AI summarizer for digesting long-form sources.
Each card below is a page in its own right - it walks through what the tool does for Data analysts and researchers, why you would reach for it over the alternatives, and answers the questions that come up most often. Click through to use the tool, or read the page first to decide which one fits.
Yes. The CSV is parsed line by line with a proper RFC 4180 tokenizer, then displayed in a virtualized table so a 100k-row file does not freeze the tab. The file is not uploaded; the parser runs entirely on your device.
Typical laptops handle a few MB of formatted JSON comfortably - say, 100k lines, 5 MB on disk. Beyond that the parse becomes slow (the formatter does not stream). For megabyte-class JSON you want jq on the CLI; for the 1-50MB range a streaming formatter is better than this one.
Yes, in the browser. It supports JavaScript regex (named groups, lookbehinds, unicode properties). For PCRE-only features (possessive quantifiers, lookbehind with backreferences) the pattern will fail at compile time with a clear error message.