Convert Files and Folders to ISO in Windows 10

Updated 5 November 2026 · Standard formula, shown below

Windows 10 can mount and open an existing ISO image, but it does not include a built-in tool for creating an ISO from ordinary files and folders. To make one, use a reputable ISO authoring utility: select the files and folders, choose the ISO format, and save the resulting image file.

What an ISO file is—and what Windows can do

An ISO is a disk image: a single file containing a filesystem and the data and folder structure of a disc or other image. The name comes from the ISO 9660 optical-disc filesystem, although ISO images can also use other filesystem formats, such as UDF. An ISO is not simply a renamed folder. Its contents are organized inside an image that software can mount, burn to a disc, or use for installation media.

Windows 10 includes features for using some ISO files, but creating one from selected files and folders is a separate task. In File Explorer, right-click an ISO and choose Mount to make it appear as a virtual drive, or choose Burn disc image if you have a compatible optical drive and want to write it to a disc. These commands do not create an ISO from a folder.

Choose an ISO creation method

For most people, a graphical ISO authoring utility is the simplest approach. Look for software that explicitly supports creating an ISO from a data folder, lets you select a suitable filesystem, and can verify or test the finished image. Download it from its publisher or another trusted distribution source, and avoid installers that bundle unrelated software.

Other options depend on what you are trying to accomplish:

Make a data ISO: Use an ISO authoring program to package files and folders into an image.
Back up files: A regular backup or archive may be more convenient. ZIP and similar archives are not ISO images, but they can be simpler to create and extract.
Make Windows installation media: Use Microsoft’s current Windows installation-media instructions and tools. A folder of setup files converted into an ISO is not necessarily equivalent to official, bootable installation media.
Burn files to a disc: If your goal is just to put files on a writable disc, Windows’ disc-burning workflow may be enough; creating an ISO first is not always necessary.

Windows PowerShell does not provide a general built-in command for authoring an ISO from an arbitrary folder. Be cautious with instructions that present a command-line method as a standard Windows 10 feature; such steps may depend on additional software or a particular Windows component.

Steps for making an ISO from folders

The precise labels vary by program, but the workflow is broadly similar. Before starting, gather the files, decide whether the image needs to work on a particular computer or disc, and make sure the destination drive has enough free space.

Install and open an ISO authoring utility. Check that the program can create an image from files, rather than only mount or burn existing images.
Start a new data-image project. Choose an option such as creating a data disc or building an ISO. Do not choose a copy-disc option unless you are copying an existing disc.
Add the files and folders. Use the program’s file browser or drag-and-drop interface. Review the project tree so you can see that the intended folders and files are included.
Choose the filesystem or compatibility settings. For an ordinary data image, a commonly supported ISO 9660 or UDF option may be suitable. If files have long names, Unicode characters, or deep folder paths, check the utility’s documentation and choose settings that preserve them.
Set a volume label if desired. This is the name shown for the disc or mounted image; it is not the ISO filename.
Choose an output location and save as an ISO. Give the file a clear name, such as ProjectFiles.iso, and make sure the program is set to create an ISO rather than burn directly to a physical disc.
Wait for the image to finish, then check it. Reopen or mount the ISO and compare its contents with the source folders. If the utility offers a verify or test function, use it when the files matter.

Some authoring programs distinguish between a standard data ISO and a bootable image. A bootable image needs suitable boot information, not merely files with names such as setup.exe or boot. If you need installation or recovery media, follow instructions intended for that specific operating system or device.

Filesystem, file names, and compatibility

The filesystem choice affects how names and files are represented and where the image can be used. Older ISO 9660 compatibility settings can impose restrictions on filenames or directory depth. Extensions such as Joliet or Rock Ridge add capabilities for names and metadata in particular environments, while UDF is common for newer optical-media uses. Support varies among operating systems, devices, and authoring tools, so there is no one setting that is best for every situation.

Check the requirements of the destination device before building the image. For example, a device expecting a particular disc format or a bootable image may not accept an otherwise valid data ISO. Also consider file-size limits of the selected format and the tool; support for large files depends on the filesystem and implementation.

Common problems and safe handling

The ISO option is missing: The program may be in a burning or copying mode rather than an image-authoring mode. Start a new data-image project and look for an ISO output setting.
Files or folders are missing: Review the project contents before saving, then mount the finished image and inspect it. Do not assume a successful save means every intended item was included.
Names look different: This can result from filesystem restrictions or compatibility settings. Try an option that supports the required names and check the image on the target system.
The ISO will not boot: A data ISO is not automatically bootable. Use a suitable boot-image workflow and follow the target system’s documented requirements.
The image is too large or will not fit: Check the destination’s free space and the limits of the selected filesystem or disc. An ISO stored on a hard drive is not limited to the capacity of a CD or DVD, but the format and software can still impose constraints.

An ISO is a container, not encryption or a backup guarantee. Anyone who can access an unencrypted image may be able to read its files. Keep another copy of important data, use trusted software, and scan downloaded files with your usual security tools. If you share an ISO, provide its source and, where available, a checksum from a trustworthy source so the recipient can check whether the file changed.

Frequently Asked Questions

Can Windows 10 create an ISO from a folder without extra software?
Windows 10 can mount and burn certain existing ISO images, but it does not include a general built-in feature for turning an arbitrary folder into an ISO. Use an ISO authoring utility for that task.

Can I make an ISO by renaming a ZIP file?
No. Changing a file extension does not convert the file’s internal format. A ZIP archive remains a ZIP archive; an ISO authoring program must build an image with an appropriate filesystem.

How do I open or check an ISO in Windows 10?
In File Explorer, right-click the ISO and select Mount if that option is available. Windows shows it as a virtual drive, which you can open to inspect its contents. Right-click the virtual drive and choose Eject when finished.

Will an ISO made from a folder be bootable?
Usually not just because it contains operating-system files. Bootability requires appropriate boot information and compatible image settings. Use instructions and tools designed for the intended installation or recovery media.

Is an ISO the same as a backup?
No. An ISO can hold a copy of files, but it does not automatically provide backup features such as scheduled copies, version history, or recovery checks. Keep a separate backup if the data is important.

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.