Overview
UltraISO does something most image tools cannot: it edits an image in place. Open an ISO, add a file, delete a folder, rename something, and save, and the image is rewritten without ever extracting it to disk and rebuilding it. For anyone who has had to slip a driver or an answer file into an installation image, that alone is the reason it stays installed.
Format handling is broad. It reads the common image formats produced by other burning software and converts between them, which is the usual fix when a download arrives in a format nothing else on the machine will open. Images can be made directly from a physical disc, from a folder tree on disk, or built up file by file with the boot information set manually.
The bootable media side is what most people use it for now that optical drives have disappeared. Write an installation image to a USB stick with the boot sector handled correctly, choose the write method for stubborn firmware, and hide or verify the result afterwards. It also mounts images to virtual drives so an installer runs without any media at all, and it can still burn to a disc where one is required.
What it does well
Edit images in place
Add, remove and rename files inside an ISO and save it back without extracting and rebuilding the whole image.
Format conversion
Read and convert between the common disc image formats so a file from any burning tool opens on this machine.
Bootable USB writing
Write installation images to a USB stick with the boot sector handled correctly, and choose the write method for awkward firmware.
Virtual drives
Mount an image to a virtual drive so installers and disc based software run with no physical media.
Image creation
Build an image from a physical disc, from a folder tree, or file by file with boot information set manually.
Changes in this build
- Improved handling of very large images above the older size limits.
- USB writing updated for current firmware that rejects older boot sector layouts.
- Faster conversion between image formats on solid state drives.
- Virtual drive component rebuilt for the current driver signing requirements.
- Fixed a corruption case when editing images containing long path entries.
What is in the package
- UltraISO Premium installer, 32 and 64-bit
- Virtual drive driver components
- Bootable media writing modules
- Format conversion components
- Multilingual interface files, 28 languages
System requirements
| Processor | Any x86 or x64 processor |
| Memory | 512 MB |
| Graphics | Not applicable |
| Storage | 20 MB free plus room for the images you work on |
| Display | 1024 x 768 minimum |
| System | Windows 7 through Windows 11, administrator rights for virtual drives |
Installation
- Extract the archive to a local folder.
- Run the installer with administrator rights so the virtual drive driver registers.
- Apply the included configuration step before first launch.
- Reboot if the virtual drive does not appear immediately.
- Open an image once to confirm the file associations took.
Before you start
Editing an image invalidates any checksum published with it, note the original before changing anything.
Writing to USB erases the target stick completely, check the drive letter twice.
Some very new firmware refuses older boot layouts, try the alternative write method if a stick will not boot.
Questions about this title
Can it edit an ISO without extracting?
Yes, files can be added, removed and renamed inside the image and saved back directly.
Does it make bootable USB sticks?
Yes, with several write methods for firmware that rejects the default layout.
Can it mount images?
Yes, virtual drives are included so an installer runs with no physical media.
Which formats does it read?
The common disc image formats from the major burning tools, with conversion between them.
About this listing
This entry was checked on a clean install of Windows 7 / 8 / 10 / 11 before it was published, and it is rechecked whenever the package is rebuilt. The figures on this page come from the site index rather than from the publisher, so the download count is what people here have actually pulled.
If a mirror stops answering, use the contact form and it gets replaced. Reports about a specific title are handled faster than general messages because they name the file, the mirror and the point at which the transfer stopped.
Requests for a different version, a different language build or an older release go on the requests page. Older versions of a title are usually still held even when only the current one is listed.