500 KB TXT sample file

A TXT file of exactly 512,000 bytes. It is a valid Plain text file, generated for this site and checked with an independent parser.

Download

sample-txt-500kb.txt

500 KB512,000 bytes

Download 500 KB TXT

Direct download. No sign-up and no waiting.

Type
text/plain
SHA-256
834e70acef70b78524156b16fc5f1244f2d0815edc13c3b1ec5981619ca3f90b
Direct URL
https://sampletestfiles.com/downloads/txt/sample-txt-500kb.txt

What is in this file

5,148 numbered lines of plain English text, each prefixed with its line number and starting byte offset so truncation is easy to spot. A closing rule of "=" characters brings the file to the exact size.

Numbered lines5,148
EncodingUTF-8 (ASCII characters only)
Line endingsLF (Unix)

How the file begins

The opening lines of sample-txt-500kb.txt, exactly as they appear in the file.

SampleTestFiles sample text file (500 KB)
Encoding: ASCII, which is also valid UTF-8. Line endings: LF.
Each numbered line starts with its line number and the byte offset at which it begins.

0000001 000000192 This sample file exists so that software can be tested with realistic input.
0000002 000000287 Every line in this document was generated by a script and describes nothing confidential.
0000003 000000395 Use it to check that uploads, downloads and parsers behave the way you expect.
0000004 000000492 The file was built to an exact byte count, which makes size limits easy to verify.
0000005 000000593 If the last line of this file is missing, the transfer was cut short.
0000006 000000681 A good test fixture is boring, predictable and identical every time it is downloaded.
0000007 000000785 Compare the checksum published on the download page with the one you compute locally.

Preview

Shows the first 64 KB of the file.

Where 500 KB matters

A 512,000-byte file: larger than most API body limits, smaller than most upload limits. These are the default limits a file of this size is useful for testing:

SystemLimitNote
Amazon DynamoDB items400 KB per item500 KB cannot be stored as a single item.
Express body parsers100 KB by defaultRejected unless the limit is raised.
nginx request body1 MB by default (client_max_body_size)Accepted with room to spare.

All 500 KB sample files

Use this file for

  • Testing that APIs return 413 for oversized bodies
  • Testing line-ending normalisation
  • Measuring transfer speed with compressible content

Testing notes for TXT

  • Plain text compresses very well, so a 10 MB text file may travel as a fraction of that when gzip or Brotli is enabled. Use the BIN samples when you need incompressible bytes.
  • Line endings change the byte count: converting LF to CRLF adds one byte per line, which breaks checksum comparisons.

TXT format reference

Technical details

File namesample-txt-500kb.txt
FormatTXT (Plain text)
Extension.txt
MIME typetext/plain
Size512,000 bytes (500 KB)
KindText
SHA-256834e70acef70b78524156b16fc5f1244f2d0815edc13c3b1ec5981619ca3f90b
Created2026-10-10
ValidationExact size, signature bytes and structure checked when the file was generated
PreviewAvailable on this page
SourceGenerated for this site; not copied from elsewhere
LicenceFree to use, modify and redistribute (terms)
CategoryDocuments

Validated for expected format and integrity. As with any download, scan the file with your own security tools before opening it. How files are made and checked

Download from the command line and verify

Fetch the file with curl, then compare its checksum with the SHA-256 value above.

curl -o sample-txt-500kb.txt 'https://sampletestfiles.com/downloads/txt/sample-txt-500kb.txt'
sha256sum sample-txt-500kb.txt     # Linux
shasum -a 256 sample-txt-500kb.txt # macOS

On Windows, run Get-FileHash sample-txt-500kb.txt -Algorithm SHA256 in PowerShell. A matching value proves that the download is complete and unaltered.

Related files

Questions about this file

Is this file exactly 500 KB?
Yes. It is 512,000 bytes, which is 500 KB in the binary units that operating systems and server limits use (1 KB = 1,024 bytes).
What is inside the 500 KB TXT file?
5,148 numbered lines of plain English text, each prefixed with its line number and starting byte offset so truncation is easy to spot. A closing rule of "=" characters brings the file to the exact size.
Why does each line start with numbers?
Each line carries its line number and the byte offset where it begins. If a transfer is truncated or corrupted you can see exactly where.