ImgBurn records optical discs and creates or checks disc-image files. A disc image stores the sector layout and file-system structure that a burner writes to a CD, DVD, HD DVD, or Blu-ray medium. This differs from copying ordinary files into a folder, and it also differs from authoring a movie menu. ImgBurn can turn a prepared folder into an image or disc, but it does not design the video project that produced that folder.
Five modes divide work
Read mode copies a physical disc into an image file. Build mode takes files and folders from local or network storage, arranges them into a disc file system, then sends the result to an image file or a burner. Write mode starts with an existing image file and records it on compatible media. Verify mode rereads a disc, while Discovery mode exercises a drive and blank medium for quality testing.
The mode matters because each screen expects a different source. Selecting Write for a folder produces the wrong workflow; ImgBurn needs Build for that job. Selecting Read does not extract one chosen document from a disc. It reads the disc as an image, so the destination needs enough free space for the complete result.
Build chooses output
Build can save an image on the computer or write the compilation directly to a physical device. Saving the image creates an intermediate file that can be inspected, stored, or burned later. Direct device output removes that intermediate step, but it also makes the chosen burner and blank medium part of the same operation.
ImgBurn has Standard and Advanced input views for Build. A saved Build project keeps the selected files and settings for later use. It does not embed the source data inside the project file, so moving or deleting an original folder can break a later rebuild. Network sources add another constraint: a remote drive that reports FAT or FAT32 can trigger four-gigabyte splitting unless the related file-input option changes.
Verification has limits
Verify can check whether every sector remains readable. It can also compare the disc with a selected image file so the check covers the recorded data rather than readability alone. A successful result confirms that the drive read the expected sectors during that pass. It does not promise that scratched media will remain readable later or that every other drive will accept the disc.
The Verify choice after a burn rereads the new disc and compares it with the source. Skipping it saves time but removes the immediate check that catches unreadable sectors or a mismatch. Software that changes disc data while ImgBurn reads it can also create a false comparison failure, so the official changelog identifies disc-filter programs as possible interference.
Media controls methods
ImgBurn exposes Incremental, Track-at-once, Session-at-once, and Disc-at-once writing methods where the selected disc and drive support them. The method cannot make unsupported hardware accept a medium. Write speed has the same dependency: choosing the highest number does not guarantee the cleanest recording, while choosing a speed absent from the drive and media combination leaves firmware to select another behavior.
A synchronization setting can copy write speed, copy count, Test Mode, and Verify choices between Build, Write, and Discovery. This can save repeated setup, but a test choice made in one mode may appear in another later. Check the visible options before starting a real burn rather than assuming each mode retained an independent value.
Discovery consumes media
Discovery performs a destructive dummy burn across a blank disc and records graph data for compatible analysis software. It is for testing the combination of writer and medium, not for recovering files or checking an already written archive. The operation consumes recordable media when the laser writes it.
Test Mode follows the command sequence without turning on the laser. It can reveal whether the computer supplies data fast enough and whether the drive accepts the commands, but it cannot measure actual burn quality. Plus-format recordable and rewritable media do not support this test path. ImgBurn therefore needs a real Discovery write when the question concerns the physical result rather than command flow.
