Getting started: How the URLs work, and how to fetch a fixture from the command line, a GitHub workflow, a pytest suite or your own code, then verify its SHA-256.
Naming and sizes: The fixture naming grammar, why kb and kib are different sizes, how exact a size is, how HLS is named, and why a published file's name never changes.
HTTP contract: Every header, status code and caching rule loremfile.dev promises: the URL scheme, methods, CORS, immutability and what clients should expect.
Manifest and discovery files: manifest.json, sha256sums.txt, per-format indexes, llms.txt, robots.txt, sitemap.xml and security.txt: what each file holds and the rules for it.
Use it from your language: Fetch a fixture and verify its hash in shell, Python, JavaScript, Go and Java, with examples that run in CI against this site on each change.
MCP server: Connect an agent to loremfile.dev with the npx or uvx config, then use its three read-only tools to list fixtures, describe one and verify a local file.
FAQ: Answers on hotlinking, rate limits, why there is no ?download parameter, why search engines skip the files, mirroring, stability and where files come from.
Contributing: How to request a fixture, the naming grammar, what loremfile will not accept, and what a generator, a test and a dependency need before a change merges.
Security policy: How to report a vulnerability in loremfile.dev through GitHub private reporting or email, the 7-day acknowledgement, no bounty, and what is in scope.