CSV to XML is a text transform, not a lock
A partner asked for XML and your export is a CSV.
Each row becomes an element in the browser. The first row is treated as the field names. A comma inside a cell splits the row if the quotes are wrong.
Do not treat this as security
XML from this page is a simple dump, not a legal invoice schema. Check the field names before you send it. The text never leaves the browser.
CSV to XML without the extra promises
CSV to XML sits on this site because CSV and XML are not interchangeable, even when they look similar in a file list. A partner asked for XML and your export is a CSV. Mail merges, databases, and Google Sheets imports are typical CSV jobs. Partners who publish an XML schema ask for it even when you exported CSV or JSON.
Each row becomes an element in the browser. The first row is treated as the field names. A comma inside a cell splits the row if the quotes are wrong.
Read this about CSV before you upload
CSV is one table in text: a row per line, commas between cells. Databases and import forms accept it. A comma inside a name splits one column into two unless the field is quoted. Extra sheets disappear.
Keep the workbook. CSV is not a backup of formulas.
Read this about XML before you send the download
The download has to be XML, because that is the format the next step named. Partners who publish an XML schema ask for it even when you exported CSV or JSON. Tags can describe nested records better than a flat table.
Read a sample record before you post the file to a live system.
Keep, check, then delete
People lose time when they convert before they know which rule failed. Size, pixel dimensions, codec, font encoding, and layout are different rules. CSV to XML only addresses the CSV to XML step. A partner asked for XML and your export is a CSV. Each row becomes an element in the browser. The first row is treated as the field names. A comma inside a cell splits the row if the quotes are wrong. XML from this page is a simple dump, not a legal invoice schema. Check the field names before you send it. The text never leaves the browser. The text stays in the browser. Try one line you can check before a whole document. Do not paste passwords. Do the test with a short or simple file first when the real file is large. A one-page PDF, a single photo, or a one-minute clip will show you whether the output is the kind of file you needed. After that test looks right, run the real file once. Keep both the CSV original and the XML download until the receiving person or the upload form accepts it. CSV to XML is a text transform for a payload you already understand. Encoding is reversible on purpose. It is not a lock, not a password store, and not a place for production secrets. Check the output before you paste it into a live request, and do not run the tool twice on text that was already encoded.
Here is the decision for CSV to XML. You start with CSV and you stop when a real program accepts XML. Almost every data tool can read a simple CSV. A browser conversion produces a simple dump, not a legal invoice schema with namespaces. If those two sentences describe a tradeoff you do not want, do not convert. Renaming the extension by hand will not do this job. Running the tool twice on its own output will not do it either.
XML from this page is a simple dump, not a legal invoice schema. Check the field names before you send it. The text never leaves the browser.
A related step, if you still need one, is XML to CSV.
Other jobs start from the homepage, where each tool is named for the conversion it actually does.