Basic text filePopular
sample.txtShort, readable plain-text file in UTF-8 with Unix line endings.
- 1.0 KB
- UTF-8
- LF
Plain text files at exact byte sizes and in tricky encodings. Ideal for upload limits, parsers, line-ending bugs and encoding detection.
Short, readable plain-text file in UTF-8 with Unix line endings.
Exactly 1,024 bytes of readable text (1 KiB, binary units). For precise size-limit tests.
Exactly 102,400 bytes of readable text (100 KiB, binary units). For precise size-limit tests.
Exactly 1,048,576 bytes of readable text (1 MiB, binary units). For precise size-limit tests.
Exactly 10,485,760 bytes of readable text (10 MiB, binary units). For precise size-limit tests.
Twenty-two scripts, emoji with skin tones and ZWJ sequences, RTL text and tricky invisible characters.
The Unicode sample encoded as UTF-16 little-endian with a byte-order mark. Catches encoding-detection bugs.
Every line ends with CRLF. Tests parsers, diff tools and checksums that assume LF.
A completely empty file. Tests zero-byte validation and empty-state handling.
Create a valid TXT file of any exact size, byte for byte, right in your browser. Nothing is uploaded, and you can generate as many as you like.
| Extension | .txt |
|---|---|
| MIME type | text/plain |
| File signature | None (plain text). UTF-8 BOM EF BB BF and UTF-16 BOM FF FE are optional |
| Origin | ASCII, 1963 · Unicode, 1991 |
| Files here | 9 · 11.1 MB in total |
| License | Free for any use, no attribution |
A TXT file holds plain characters with no formatting. It has no signature, so software has to guess its encoding. UTF-8 is the modern default; UTF-16 files usually begin with a byte order mark.
Windows ends lines with CRLF (\r\n) while macOS and Linux use LF (\n). Mixing the two is a classic cause of diff noise and parsing bugs.
with open("files/txt/sample-utf16.txt", encoding="utf-16") as f:
print(f.read(200))curl -O https://samplefiles.technologychannel.org/files/txt/sample.txtYes. The size-named files are exactly that many bytes, so they are reliable for testing limits at the boundary. The file list shows the precise byte count.
Zero-byte files break more code than you might expect: upload forms, hash functions, parsers and progress bars. It is the quickest edge case to test.
Yes. Every text file here is free for any use, including commercial testing, demos and tutorials. No attribution is required.
Yes, as many times as you like. There is no sign-up, no daily limit and no waiting timer. Direct links also work in scripts, CI jobs and automated tests.