Sample TXT files
| Filename | Encoding | Line endings | Size | Use this to test | Download |
|---|---|---|---|---|---|
| sample-utf8-lf.txt | UTF-8 | LF | 42 bytes | Check a basic UTF-8 upload with Unix line endings. | |
| sample-utf8-crlf.txt | UTF-8 | CRLF | 44 bytes | Compare Windows line ending handling with the LF example. | |
| sample-utf8-bom.txt | UTF-8 with BOM | LF | 45 bytes | Check recognition or removal of a UTF-8 signature. | |
| sample-utf16-le.txt | UTF-16 LE | LF | 86 bytes | Verify a reader that expects little-endian UTF-16 with a BOM. | |
| sample-ascii.txt | ASCII | LF | 52 bytes | Check a reader restricted to ASCII characters. | |
| sample-empty.txt | UTF-8 | None | 0 bytes | Check validation of a genuinely empty attachment. | |
| sample-multilingual.txt | UTF-8 | LF | 69 bytes | Test accented letters, multiple scripts, and emoji. | |
| sample-1mb.txt | UTF-8 | LF | 1000000 bytes | Try a decimal 1 MB upload or preview boundary. | |
| sample-tab-separated.txt | UTF-8 | LF | 37 bytes | Verify tab-delimited columns and a header row. | |
| sample-log.txt | UTF-8 | LF | 131 bytes | Test line-based parsing with fictional log records. |
Choose a file for your test
Use these examples when you need a known input before working with your own documents. Each download is generated in your browser, with the encoding, line endings, and byte count shown in the list. No account is required. Keep a note of which example you use and what your application does with it.
For an upload form, start with the small UTF-8 example to check that a normal text attachment is accepted. Try the empty file to find out whether the form requires content as well as a valid extension. The large example contains exactly 1,000,000 bytes, or 1 MB in decimal units. It is useful for trying a size boundary or checking that a preview does not attempt to display the entire document at once. It is smaller than 1 MiB, which is 1,048,576 bytes.
Test character encoding
UTF-8 is a practical starting point for new documents. Its basic English letters share byte values with ASCII, while accented characters, Chinese, and emoji use additional bytes. The multilingual example helps expose readers that appear to work with English but misinterpret other characters. Compare the saved text with what your application displays, rather than assuming that a successful upload means the characters were decoded correctly.
The UTF-8 BOM example begins with the three-byte signature EF BB BF. Its body is still UTF-8. Some import programs use that signature to select a decoder; others may accidentally include it in the first field. The UTF-16 LE example begins with FF FE and stores 16-bit code units in little-endian order. Choose it when checking a reader that explicitly supports that encoding. The ASCII example contains only ASCII characters. For background, read what a TXT file is.
Compare line endings and structured text
LF represents a line break with one byte, 0A. CRLF uses two bytes, 0D 0A. The two small UTF-8 examples contain the same words with different line endings, making them useful for comparing line counts and imports. A wrapped line on screen does not necessarily mean a newline exists in the file. Read the CRLF and LF guide for more detail.
The tab-separated example uses actual tab characters between fields. Try it with an importer that accepts tab-delimited text, checking both the column count and the header row. The log example contains fictional timestamps and status messages for testing previews, search, and line-based parsing. These are plain text examples, so a program may still require its own schema or additional validation rules. The empty sample has no BOM and no newline: its size is truly zero bytes.
Make your own example
Need different content or a particular filename? Use the home page editor to type or paste your own text, choose an encoding and line ending style, and download a local copy. Test with representative characters and a few realistic records before importing a much larger document. Keep your original file so you can compare the result after editing or converting it.