Just characters and an encoding
A plain-text file stores nothing but characters, which sounds simple until you ask how those characters are represented as bytes. That mapping is the encoding. Modern files overwhelmingly use UTF-8, which covers every script and emoji while staying compatible with the old ASCII range, but older files might use Latin-1, Windows-1252 or a regional code page. There is usually no marker inside the file announcing which encoding was used, so a program has to guess — and when it guesses wrong, accented letters and symbols turn into garbled sequences. Saving as UTF-8 is the safest default for anything that might travel between systems.
The line-ending quirk
The other classic gotcha is how lines end. Windows marks the end of a line with a carriage return followed by a line feed, while macOS and Linux use a line feed alone — a difference inherited from decades-old conventions. Most modern editors handle either silently, but move a file between systems with older tools and you may see every line run together, or stray characters appear at line ends. It is harmless once you know to look for it, and most editors can convert line endings with a single setting.
Strengths
- Opens on absolutely everything, from ancient terminals to modern phones.
- No hidden formatting, macros or tracking — what you see is exactly what is stored.
- Tiny files that compress well and survive decades without becoming unreadable.
- Ideal source for scripting, search and automated processing.
Limitations
- No formatting at all — no bold, no headings, no images, no styling.
- Encoding ambiguity can turn accented text into unreadable symbols.
- Line-ending differences between operating systems still cause occasional glitches.
- Structure exists only as far as your own spacing and punctuation imply it.
When to use Text
Reach for plain text when you want maximum portability and longevity, or when the content is for reading or processing rather than presentation.
Text FAQ
- Why does my TXT file show weird characters?
- The file was almost certainly saved in one encoding and opened as another, so the bytes are being misinterpreted. Reopening it as UTF-8 — or as the original encoding, often Windows-1252 — usually restores the correct characters.
- What is the difference between TXT and a Word document?
- A TXT file holds only characters with no formatting, while a Word document stores fonts, styles, images and layout in a structured package. Plain text is far more portable but cannot carry any visual design.
- Can I convert a TXT file into a formatted document?
- Yes, though TXT carries no formatting to preserve, so a conversion mainly wraps the text into a new container. Morphr can move plain text into formats like Markdown or DOCX in the browser, where you can then add structure.