Free ISO test files and sample generator
A CD/DVD disc image with a real ISO-9660 filesystem. Generate valid .iso sample files to test mounting, burning tools, virtual drives, extractors and upload handling.
What is a .iso file?
ISO: ISO-9660 Disc Image. An ISO is a complete filesystem image of an optical disc, using ISO-9660. It is how operating systems and large software bundles are distributed, and it can be mounted directly by every modern OS.
Why generate a test ISO file?
- Test mounting, extraction or burning tooling.
- Verify a virtualization or provisioning step that attaches disc images.
- Exercise large-file handling in upload or storage paths.
What you can put inside a .iso file
You get 3 content options for ISO, so the file holds something meaningful rather than random padding: Text files, Mixed file types, Many small files. For ISO these are alternatives, so choose the one that matches what you need to test.
How a .iso file is identified
Every .iso file begins at offset 32769 with 43 44 30 30 31, "CD001" at offset 32769. The first 32 KB is a reserved system area, so the identifier sits in sector 16. That is what a validator inspecting content rather than the file name looks for.
How the size lands on the exact byte
A disc image is a whole number of 2048-byte sectors, so size is set in sectors and one file absorbs the remainder. A non-aligned target leaves bytes past the declared volume size, where readers stop.
Negative testing with broken ISO files
- Invalid. Identifiable, but wrong inside, so it fails during parsing.
- Corrupted. The leading bytes are destroyed, so the
43 44 30 30 31identifying a .iso is gone. Same length as the valid file. - Incomplete. Truncated part-way, so it is genuinely shorter.
- Empty. Chosen under Content rather than File Condition: valid structure, no data.
Which failure to reach for, and what to assert for each, is covered in how to make a corrupted file for testing. For upload limits and type checks see testing file upload validation.
Sample ISO content
[ISO], 2048-byte sectors: system area, Primary Volume Descriptor (sector 16), path tables, root directory, file data.
This shows the shape of the file. Your download is generated fresh at the size you choose, so the values will differ.
How to open and verify the file
Mount it, on Windows double-click or `Mount-DiskImage`, on Linux `mount -o loop`, on macOS `hdiutil attach`. 7-Zip also extracts it.
Media type application/x-iso9660-image · extension .iso · category Archives
Generate a .iso file → · questions about sizes, privacy or cost are answered on the site FAQ.
Frequently asked questions about ISO files
What identifies a .iso file?
A .iso file begins at offset 32769 with the bytes 43 44 30 30 31, "CD001" at offset 32769. The first 32 KB is a reserved system area, so the identifier sits in sector 16. Those bytes are what a content-sniffing validator looks for, and what the Corrupted condition destroys.
How can a .iso file be an exact number of bytes?
A disc image is a whole number of 2048-byte sectors, so size is set in sectors and one file absorbs the remainder. A non-aligned target leaves bytes past the declared volume size, where readers stop.
What can go inside the ISO file?
There are 3 content options for .iso: Text files, Mixed file types, Many small files. For ISO these are alternatives, so pick the one matching what you need to test.
Can I download several broken ISO files at once?
Yes, select more than one File Condition and you get one ZIP containing a .iso per condition, each named after its condition.
Can the ISO file use UTF-16 or a byte-order mark?
No, and deliberately. A .iso file is a container rather than plain text, so rewriting its bytes as UTF-16 would not produce a UTF-16 document. It would produce a broken file. Use a text format such as CSV, JSON or XML for encoding tests.
How do I open or verify the ISO file?
Mount it, on Windows double-click or Mount-DiskImage, on Linux mount -o loop, on macOS hdiutil attach. 7-Zip also extracts it.