Licence, provenance and safety policy (CC0 / Public Domain)

How every sample file on SampleTestFiles is created, what licence applies to your downloads, why unavailable formats are never faked, and why executable files are never hosted on our server.

1. Public Domain / CC0 1.0 Universal dedication for all sample files

Every downloadable sample file, synthetic dataset, broken-file fixture, media edge-case clip, and mock JSON file published on SampleTestFiles is generated by our own first-party build scripts and in-browser generators and is dedicated to the public domain under CC0 1.0 Universal (Public Domain Dedication).

2. Why proprietary and camera RAW formats are marked unavailable rather than faked

Some file-download websites trick search engines by taking a standard JPEG or TIFF image, renaming its file extension to .cr2, .nef, or .psd, and serving it as a "sample file". When a developer feeds that faked file into LibRaw, ExifTool, or Adobe Photoshop, the parser immediately fails or silently takes the wrong code path.

Our policy is strict: we never ship a file whose bytes do not match its declared extension and MIME type. Whenever a format cannot be produced deterministically by open-specification tools—specifically win.rar GmbH's proprietary .rar compressor, RealNetworks' proprietary .rmvb/.ra encoders, layered .psd/.xcf project files, and physical digital camera sensor dumps (.cr2, .nef, .arw, .orf, .raf, .rw2, .x3f, .dng)—we document its magic-byte signature and structure on our All Formats A–Z and Tier 2 Family pages and mark it Unavailable with the exact technical reason.

3. Why executable binaries (.exe, .iso, .class, .jar) and EICAR are never hosted

Hosting downloadable Windows executables (.exe), optical disc images (.iso), compiled Java bytecode (.class, .jar), or the EICAR antivirus test string on a public web server causes two serious problems for visitors and site operators:

  1. Enterprise proxies, endpoint detection and response (EDR) agents, and browser Safe Browsing filters quarantine the download or flag the entire domain as a malware distributor.
  2. Developers accidentally running a downloaded binary on a workstation risk executing untrusted code.

To let QA engineers test upload extension blockers and magic-byte filters without any security risk, we offer .exe and .iso exclusively through our In-Browser Inert Stub Generator. Those stubs are created locally in your browser memory, contain only the leading magic signature (MZ or \x01CD001) plus a plain-text non-executable notice, and are never hosted on our servers.

4. Operator and contact information

SampleTestFiles can be reached by email. For licence verification letters, error reports, or security inquiries, email contact@sjwebtechwork.com or visit our Contact and File safety pages.

How to verify file headers and checksums locally before use

Every fixture downloaded from this library can be verified offline before you add it to a repository or test runner. First, check the file size in bytes against the figure printed in the download table. Second, compute the SHA-256 hash using sha256sum on Linux, shasum -a 256 on macOS, or Get-FileHash on Windows PowerShell, and compare the 64-character hexadecimal string against our master manifest in /checksums.txt or /files.json. Third, if you want to inspect the leading magic bytes and container structure without installing command-line tools, drop the file into our in-browser Magic-Byte File Inspector, which reads the first 64 bytes locally in your browser memory and compares the signature against the file extension.