Frequently asked
questions

Because there is no server bill to pay per file. Everything runs on your device; hosting is a handful of static files on a free CDN. No upload bandwidth means no artificial limits, no 'Pro' tier gating your own data.

Three independent ways: (1) Open DevTools → Network while using any tool — you will see zero requests. (2) Load the page, disconnect from the internet entirely, then run every operation — it all works. (3) Inspect the Content-Security-Policy header: connect-src 'none' makes outbound requests technically impossible.

It ceases to exist. Files live only in your browser tab's memory. There is no server-side copy because there is no server-side anything.

Yes — safer than upload tools by construction. GDPR concerns arise when personal data leaves your control; here no transfer occurs at all, so no processor agreement or disclosure applies. Your processing stays inside your organization's own hardware.

There are no artificial caps. Practical limits come from your device memory: modern laptops comfortably handle files with millions of rows (often hundreds of MB). If your machine can open the file, our tools can usually process it.

RFC 4180 quoting (commas, double quotes, line breaks inside fields), semicolon and tab delimiters common in EU locales, UTF-8 encoding, and preservation of leading zeros in SKUs, ZIP codes and phone numbers.

Native .xlsx round-trips are next on the roadmap — built locally like everything else, with explicit leading-zero and date-formatting protection. Until then, save as CSV first.

Yes — pages are fully responsive. Very large files are better suited to desktops simply due to available memory.