format
Plain text
TXT is unformatted text, readable by every program ever written.
Also known as TXT.
Convert a file nowWhat is a Plain text file?
Raw characters with no styling, layout or embedded media — the lowest common denominator of document formats.
Technical characteristics
- Representation
- text
- Encoding
- UTF-8 (or legacy code pages)
- Lossy
- No
- Open specification
- Yes
Compatibility
- Windowsfull
- macOSfull
- Linuxfull
- Androidfull
- iOSfull
Advantages of Plain text
- Opens anywhere, forever
- Tiny
- Diff-friendly and version-control native
Limitations to know about
- No formatting, images or structure
- Encoding ambiguity between UTF-8 and legacy code pages
When to use Plain text
- Notes
- Logs
- Data exchange
- Long-term archiving
Convert Plain text files
Plain text scores
Deterministic scores calculated from the structured facts above. Identical facts always produce identical scores.
Overall score
72/100
Archiving score
100- the specification is public, so a decoder can always be rebuilt
- the specification is published openly
- it is actively maintained and current
- an openly specified format can be implemented without a licence negotiation
Confidence 44% · evidence coverage 89%
Openness score
100- the specification is published openly
- an openly specified format can be implemented without a licence negotiation
Confidence 32% · evidence coverage 100%
Longevity score
96- it is actively maintained and current
- the specification is published openly
- the specification is public, so a decoder can always be rebuilt
- it sits at the centre of the format ecosystem, with many documented relationships
Confidence 49% · evidence coverage 100%
Printing score
83- lossless data means no compression artefacts appear at print resolution
- only a narrow set of applications handles it
Confidence 48% · evidence coverage 50%
AI score
76- open specifications are implemented by the open-source decoders that ML stacks rely on
- the specification is published openly
- large lossless payloads cost bandwidth and memory
- only a narrow set of applications handles it
Confidence 42% · evidence coverage 100%
Compatibility score
74- Windows, macOS, Linux, Android and iOS all open it without extra software
- an open specification means cloud SDKs can implement it without licensing friction
- it opens by double-clicking on every mainstream device
- only a narrow set of applications handles it
Confidence 67% · evidence coverage 75%
Editing score
51- lossless data survives repeated open-edit-save cycles without degrading
- only a narrow set of applications handles it
Confidence 45% · evidence coverage 63%
Photography score
50- lossless data survives repeated open-edit-save cycles without degrading
- it opens by double-clicking on every mainstream device
- it stores data losslessly, so files stay large
Confidence 39% · evidence coverage 44%
Web score
25- the specification is published openly
- it stores data losslessly, so files stay large
- large lossless payloads cost bandwidth and memory
Confidence 31% · evidence coverage 67%
Streaming score
0- it stores data losslessly, so files stay large
- large lossless payloads cost bandwidth and memory
Confidence 21% · evidence coverage 50%
Performance score
0- large lossless payloads cost bandwidth and memory
- it stores data losslessly, so files stay large
Confidence 21% · evidence coverage 100%
What Plain text is recommended for
Every conclusion below is derived from the structured facts on this page — nothing is written by hand.
Operating system compatibility100/100
- Because Windows, macOS, Linux, Android and iOS all open it without extra software.
- Because most platforms handle it natively.
Printing suitability100/100
- Because lossless data means no compression artefacts appear at print resolution.
- Because it is a page-description format built around fixed layout.
Cloud compatibility100/100
- Because an open specification means cloud SDKs can implement it without licensing friction.
- Because it converts into many other formats, which suits automated pipelines.
AI compatibility100/100
- Because open specifications are implemented by the open-source decoders that ML stacks rely on.
- Because lossless pixels avoid compression artefacts leaking into training data.
- Because wide library support means common data loaders can read it.
Long-term archiving100/100
- Because the specification is public, so a decoder can always be rebuilt.
- Because lossless storage preserves the original data for future migrations.
- Because it is a current, actively maintained format.
Open standards100/100
- Because the specification is published openly.
Licensing100/100
- Because an openly specified format can be implemented without a licence negotiation.
Future-proofing100/100
- Because it is actively maintained and current.
- Because open specifications outlive the companies that create them.
- Because nothing in the graph supersedes it yet.
Everyday consumer usage75/100
- Because it opens by double-clicking on every mainstream device.
- Because it is a current format that people and services still expect.
Popularity71/100
- Because it sits at the centre of the format ecosystem, with many documented relationships.
- Because every mainstream operating system handles it.
- Because it is still current rather than being phased out.
What Plain text is not recommended for
Software compatibility33/100
- Because only a narrow set of applications handles it.
Web suitability33/100
- Because lossless payloads cost more bandwidth than the web usually justifies.
Related to Plain text
Data quality
Every claim on this page is classified as a verified fact, a derived fact or an assumption.
- Overall confidence
- 80%
- Verification status
- verified
- Last reviewed
- 2026-08-03
- Verified facts
- 1
1 classified claim backed by 1 source.
- Convert Always editorial review — Convert Always
Sources and review status
Review status: verified · confidence 80%
Last reviewed 2026-08-03 (revision 1).
- Convert Always editorial review — Convert Always