How we generate sample files
TrueFileSize exists for one reason: a file named sample-10mb.pdf should behave like a real 10MB file in your upload form, parser, storage pipeline, or CI test.
Generate a real file
Format-aware generators or encoders create the catalog artifacts. Intentionally invalid, empty, or extension-mismatch fixtures are labeled as negative tests instead of being presented as valid examples.
Measure the bytes after creation
The generated file is measured after it is written to disk. The published size comes from the file record, not from the label alone.
Hash and inspect the artifact
A streaming verifier calculates SHA-256, compares the exact byte count with the catalog, and checks a known header signature where the format has one. Header matching is a format hint, not a complete parser or malware guarantee.
Publish stable download URLs
Files are served from stable URLs so test suites, CI jobs, and documentation can link to the same fixture repeatedly.
What we publish on file pages
File cards expose the filename, exact byte size, display size, MIME type, technical metadata when available, license, and stable download URL, SHA-256 checksum, header-signature result, catalog integrity status, and verification date. The evidence manifest is generated from the local release artifacts and checked for drift before a release.
See the license page for usage rights, or read our editorial policy for how we review guides and file claims.