Why systems keep asking for CSV
Plenty of software refuses .xlsx and only accepts comma-separated text: CRM importers, bank payment uploads, mailing-list tools, database loaders, and most command-line pipelines. Excel can save a CSV itself, but on Windows the default dialog buries the UTF-8 option, and choosing the wrong variant turns accented names into question marks the moment another system reads the file. This converter always writes UTF-8, so characters like é, ñ, and ü survive the trip.
What you get — and one honest limitation
Drop in a workbook and the tool exports its first worksheet as a .csv file. Only the first sheet is converted, because the CSV format can hold exactly one table — if the data you need lives on another tab, move that tab to the front, or into its own workbook, before converting. Cells are written as values, so formula cells come through as their calculated results rather than the formulas themselves.
Processed on your machine, not ours
Workbooks tend to be the most sensitive files people handle: budgets, client lists, salaries, exported bank statements. That is why the conversion happens inside your browser, with SheetJS running in a Web Worker — a background thread that parses the workbook without freezing the page. Your spreadsheet is never transmitted anywhere; there is no server side to this tool at all.
Queue multiple workbooks and two convert at a time, with a single ZIP download available when the batch finishes. There is nothing to sign up for and no daily quota, and anything above roughly 50 MB is turned away with a plain explanation, since browser memory is the only real constraint.