A Swedish CSV: the dates are already right, the numbers are not
Sweden is the pleasant case: dates are already written 2026-12-31, the international order that sorts correctly as text and cannot be read backwards. That leaves two things to fix rather than three — the semicolons between the fields, and amounts written 1 234,56 with a space between thousands.
What a Swedish file usually looks like
Saved by a spreadsheet set to Swedish (Sweden), the file has a semicolon between the fields, a comma as the decimal mark and a space between thousands, so one thousand two hundred and thirty-four and a half is written 1 234,56. Dates are written YYYY-MM-DD: the last day of 2026 is 2026-12-31.
The separator is not a character any of the numbers contain, so nothing in the file needs quoting to survive — which is exactly why the amounts and the fields can be told apart at all.
None of this is a rule the file carries with it — there is no country written inside a CSV. It is what the program that wrote the file was set to, which is why every tool here reads the bytes and says what it found rather than trusting a flag.
One problem fewer than the neighbours
Every other European page here has to warn about the date order, because 05/06/2026 means two different days depending on who wrote it. A Swedish file does not have that problem: 2026-12-31 is year, month, day, the international form, and it means the same thing to everyone who reads it. It also sorts correctly as plain text, so a column of Swedish dates comes out in the right order even before anything reads it as a date.
That is worth noticing rather than passing over, because it is the shape worth converting other files into. When a date column has been read properly, writing it back in the international form is what stops the ambiguity coming back the next time the file changes hands.
The thousands space, and the order to work in
Swedish amounts group thousands with a space: 1 234,56. Like the French case, that space is frequently a no-break space rather than the space bar character, and either way a value containing it does not read as a number. The consequence is concrete: a column holding both 410,00 and 1 234,56 falls below the bar the delimiter fixer sets for converting a column, so none of it is converted. The tool leaves the column whole instead of rewriting the half it understands.
The order that works is spaces first, conversion second. Copy the gap out of one of your own amounts and replace it with nothing in find and replace — copying rather than typing is the only way to be certain you have the same character — then run the file through the fixer, which reads the semicolons, converts the decimal commas now that the whole column qualifies, and writes a comma-separated UTF-8 copy with the count of what it changed.
The sample file
Faktura;Kund;Datum;Belopp
INV-1001;Exempel AB;2026-12-31;1 234,56
INV-1002;Modell AB;2026-03-02;89,50
INV-1003;Provfirma AB;2026-06-05;32,10
INV-1004;Urval AB;2026-11-12;24 680,00
INV-1005;Demo AB;2026-01-20;410,00
Obviously made-up data, small enough to read. Download it and drop it on the tool to see the fix before trying your own file.
Questions
- Why is my Swedish CSV separated by semicolons?
- Because Swedish settings use the comma as the decimal mark, so the list separator between values is a semicolon instead. That is correct for Sweden and unreadable to anything expecting commas.
- Do I need to convert Swedish dates at all?
- Usually not. They are already written year, month, day, which is the international order, so they sort correctly as text and no reader can take them the wrong way round.
- Why did my amounts come through unchanged?
- The thousands spaces stop the values reading as numbers, so the column does not qualify for conversion and is left exactly as it was rather than partly rewritten. Take the spaces out and it converts.
- Is the gap in 1 234,56 a normal space?
- Often not: it is usually a no-break space, which looks identical and is a different character. Copy it out of one of your own values instead of typing it, or the replacement will find nothing.
- What happens to the rest of the file?
- The separator is rewritten to commas, the text is decoded by what the bytes really are, and the download is clean UTF-8 with every value that was not converted carried across exactly as written.
- Is my Swedish file uploaded anywhere?
- No. Both steps run inside this page on your own machine; the Network tab of your browser shows this site fetching its own code, never your file going out.