BurnAware writes files, audio tracks, video folders, and disc images to optical media. A project does more than copy files into a drive letter: it builds a disc filesystem or a playback structure, sends that layout to the recorder, and can compare the written result with the source. The chosen task determines whether a computer reads the disc as storage, a CD player reads it as audio, or a DVD player recognizes its video structure.
Pick the disc job
A Data Disc stores ordinary files and folders. A Boot Disc adds boot information so compatible firmware can start from the medium. Audio CD converts supported tracks into the format expected by standard CD players, while an MP3 Disc leaves compressed music as files for players that understand that format. DVD-Video writes an existing DVD folder structure; it does not edit raw clips into menus or convert an arbitrary video into a finished DVD project.
BurnAware also handles ISO images. Burn Image writes an existing image to media. Make ISO builds an image file from selected data, and Copy to ISO reads a source disc into an image. These commands act on different sources, so choosing Make ISO when the goal is to preserve a complete bootable disc may omit layout information that a direct disc image would retain.
Filesystems affect access
Data projects can use ISO, UDF, or a combined ISO and UDF filesystem. ISO has broad compatibility but carries older naming and layout constraints depending on the selected level. UDF handles newer media and larger structures more naturally, yet an old operating system or device may not read every UDF revision. The combined choice adds compatibility information at the cost of a more complex layout. BurnAware cannot make a device understand a filesystem that its firmware never supported.
The capacity indicator tracks the project against the selected medium. Disc labels and folder names still need to comply with the chosen filesystem. A project that fits by total byte count can fail if a single file exceeds that filesystem’s limit or if the target device expects a stricter directory arrangement.
Sessions and finalizing
A multisession data disc leaves room for another recording session. BurnAware can import the existing session and append new files. Finalizing closes the disc so later sessions cannot add more data. That decision is useful for compatibility and completed archives, but it cannot be undone on write-once media. A partially filled disc does not regain append ability after finalization.
Multisession also changes what a verification result means. When BurnAware verifies the latest burn, it checks files written in that session and does not recheck every older session. A successful result therefore confirms the new addition, not the health of the entire disc history. An archive that matters still needs a separate read test or another copy, especially as optical media ages.
Verification finds errors
Verify Disc reads recorded data and compares it byte by byte where a source comparison is available. It lists files that the drive cannot read. Verification can catch a bad burn, but it cannot guarantee that another player accepts the disc’s format or that the medium will remain readable for years. Playback compatibility and data integrity are separate checks.
Rewritable media can be erased or formatted for another project. Both actions are destructive. Quick erase removes the directory information faster, while a fuller operation spends more time on the medium. Neither is a backup step. BurnAware also includes recovery work for damaged or incomplete sessions, but recovery depends on the drive reading enough of the original structure; it cannot reconstruct sectors that the hardware cannot read.
