How to Convert TXT to CSV on iPhone Without an App

Converting a TXT file to CSV is one of those tasks where the honest answer is anticlimactic. Roughly half the time it is a rename, it takes ten seconds, and every site offering to do it for you as a paid conversion is charging you for changing three letters.

The other half of the time it is a genuine data problem, your file is separated by tabs or spaces instead of commas, and renaming it produces a spreadsheet with everything crammed into column A.

I build Grabio, a free Shortcut that converts media on iPhone, and I want to be upfront: Grabio does not do this one. Text file conversion is outside what it handles. But iOS itself does, using tools already on your phone, and nobody seems to write that down. So here it is.

Understand what a CSV actually is, because it changes everything

A CSV is a plain text file. There is nothing special inside it. No formatting, no compression, no binary structure. It is exactly the same kind of file as a TXT, with one rule about its contents: each line is a row, and the values on that line are separated by commas.

That single fact tells you what you are dealing with. Open your TXT file and look at one line. If it reads like Nikhil,Mumbai,42, the content is already CSV and only the file extension is wrong. If it reads like Nikhil Mumbai 42 with tabs or runs of spaces between the values, the content is wrong too, and renaming will not fix it.

Open the file first. Tap it in the Files app and it opens in a text preview. Thirty seconds of looking saves you from picking the wrong method.

Method one: rename it, when the content is already comma separated

This is the whole procedure and it uses nothing beyond the Files app.

1. Open Files and navigate to the TXT file.
2. Press and hold it, then tap Rename.
3. Change the ending from .txt to .csv, keeping the name itself the same.
4. iOS warns you that changing the extension may make the file unusable. Tap Use.csv.

Done. The file is now a CSV and Numbers, Excel, Google Sheets and every import form will treat it as one. If you cannot see the extension when you go to rename, the file name field is showing you the whole thing already, so type the ending in yourself.

This works because the extension is only a label telling apps how to interpret the bytes. The bytes did not need to change.

Method two: Numbers, when the content needs cleaning

If your values are separated by tabs, semicolons, pipes or multiple spaces, you need something that understands columns. Numbers is free from Apple, it is preinstalled on most iPhones, and it is genuinely the right tool here.

1. Rename the file to .csv as above, even though the content is wrong. This is just to get Numbers to open it.
2. Tap the file. It opens in Numbers, which attempts to work out the delimiter on its own.
3. If everything landed in one column, the delimiter guess failed. Look for the adjust-import or delimiter control that Numbers offers when opening a text file, and set it to tabs or whatever your file actually uses.
4. Check the result looks like a table with the right number of columns.
5. Tap the three dots, choose Export, then CSV.

What you get back is a properly formed CSV with real commas and correct quoting around any value that itself contains a comma. That quoting is the part people forget and it is why this route beats a find and replace for anything containing addresses or free text.

Method three: a five-action Shortcut, when you do this often

If you are converting the same kind of file every week, build it once in the Shortcuts app and never think about it again. Shortcuts is preinstalled and free.

Create a new shortcut, turn on Show in Share Sheet in its settings, accept Files as input, and add these actions in order:

• Get Text from Input, which pulls the contents of the file in as text.
• Replace Text, finding your delimiter and replacing it with a comma. Turn on the regular expression toggle and search for a tab or for a run of spaces, depending on your file.
• Set Name, giving the output a name that ends in.csv.
• Save File, with the ask-where-to-save option on, or pointed at a folder you use.

From then on, any TXT file gets converted from its share sheet in one tap. This runs entirely on your iPhone, with nothing uploaded, which is the same reason the media conversions I build run the way they do.

The catch with the find and replace approach is quoting. If any value in your data contains a comma, replacing tabs with commas produces a broken row and a spreadsheet that silently shifts columns. For simple data, numbers, dates, single words, it is perfect. For anything with addresses or sentences in it, use Numbers.

The four things that break CSVs, and how to spot them

These are the failures that make a converted file look fine on your phone and fall apart when somebody imports it.

Commas inside values. A value like Mumbai, Maharashtra needs to be wrapped in double quotes or it becomes two columns. Numbers handles this automatically. Find and replace does not.

Character encoding. A file exported from a Windows machine may be UTF-16 or Windows-1252 rather than UTF-8. The symptom is names with accents or Devanagari text turning into garbage. Opening in Numbers and exporting fresh usually normalises it.

Line endings. Windows files end lines with a carriage return and a line feed, and most tools cope, though some older importers add a blank row between every real row. Again, a Numbers round trip cleans it.

Locale. In parts of Europe, Excel expects semicolons because the comma is the decimal separator. If your recipient is there and their import breaks, this is why, and the fix is on their end with the import dialog rather than on yours.

When your data is not in a file yet

Two adjacent situations worth naming, because people arrive at this search from them.

If your data is printed on paper, scan it first. The iPhone’s built-in scanner in Notes or Files produces a clean document, and Live Text will let you select the text straight out of the result. Scanning a document to PDF covers the capture side.

If your data is a table stuck inside a PDF, turning the pages into images and using Live Text to lift the text out is the practical route on iPhone. Converting a PDF to images handles the first half. Expect to fix the column alignment by hand afterwards, because Live Text reads lines rather than tables.

Where Grabio sits, honestly

Grabio is a free Apple Shortcut for media. On-device it handles photo formats, resizing, compression, PDF work, video trimming and compression, GIF conversion, audio extraction and QR codes, all using Apple’s own Shortcuts actions with nothing uploaded. Text file conversion is not part of that set, and none of the three methods above needs it.

The one place Grabio touches this territory is the long tail. For genuinely exotic document formats, it hands off to a conversion site, and your file does get uploaded in that case. That distinction is laid out in converting any file format on iPhone. For TXT to CSV, save yourself the upload and use Files or Numbers.

If the media side is useful to you, Get the Shortcut. It is free, no account, one tap from Safari. And if it is only spreadsheets you are dealing with, the rename in Files is genuinely all you need.

Converting TXT to CSV on iPhone: FAQ

Can I just rename a TXT file to CSV?

Yes, if the content is already separated by commas. A CSV is a plain text file with a naming convention and a formatting rule, so when the rule is already satisfied the extension is the only thing that needs changing.

Why did everything land in one column after I renamed the file?

Because the values in your file are separated by something other than commas, usually tabs or spaces. The extension told the spreadsheet to expect commas, it found none, and treated each line as a single value. Open it in Numbers and set the delimiter properly.

Do I need to buy an app to convert TXT to CSV on iPhone?

No. The Files app renames, Numbers is free from Apple and handles delimiters and quoting, and Shortcuts is preinstalled if you want to automate a repeat job. Paid converters for this task are charging for something iOS already does.

How do I handle values that contain commas?

They need to be wrapped in double quotes so the importer knows the comma is part of the value. Numbers does this automatically when you export to CSV. A manual find and replace does not, which is why it is only safe for simple data.

Why do accented or Hindi characters look like garbage after converting?

That is a character encoding mismatch, usually a file saved as UTF-16 or a Windows encoding being read as UTF-8. Opening the file in Numbers and exporting a fresh CSV normalises the encoding and generally fixes it in one pass.

Will the converted file work in Excel and Google Sheets?

Yes. CSV is about as universal as file formats get. The only common friction is regional, where Excel in some European locales expects semicolons rather than commas, which the recipient resolves in their own import dialog.