What a Float32 DNG panorama contains
A panorama exported as Float32 DNG can retain negative and above-one scene-linear RGB values that survive the stitch. Those values give you room to adjust exposure or continue linear work before you render a display-ready file.
The export is a demosaiced RGB panorama. It does not store the original Bayer mosaic from each camera photo, preserve the original sensor files, or make the stitched image a new camera RAW capture. Keep the source DNGs and project recipe if you may need to realign or change the composition.
That headroom comes from the input and processing. It cannot recreate detail that every source channel clipped at capture, or detail that was absent from a preview used as input.
When 16-bit TIFF is the better fit
Choose 16-bit TIFF when your next step is in a color-managed photo editor and you want a familiar RGB master with fine encoded gradations. The embedded profile identifies the panorama's color space, and TIFF can keep transparent coverage around areas no source photograph covered.
TIFF16 stores integer values in a finite output range. Values below zero or above the supported range are clipped at export, so it does not keep the full extended range of a Float32 scene-linear file. Lower exposure before export if you need to bring retained highlights into the integer range, then inspect the result.
TIFF16 does not add source detail. An 8-bit JPEG or preview remains an 8-bit source even when saved into a higher-bit-depth container.
The choice is about the next editing step
Use Float32 DNG when the editor you intend to use can open this linear DNG output and your workflow benefits from values outside the ordinary display range. Compatibility varies by editor and version, so test a small export in your own workflow before committing a large project.
Use 16-bit TIFF when predictable color-managed editing and broad interchange matter more than retaining values outside the integer range. For retouching or compositing, TIFF16 is often practical, especially when the panorama needs transparent gaps.
Neither format is automatically an HDR photograph for every viewer. The file's values and the receiving editor's interpretation both matter.
Check the source before exporting
For camera DNG input, inspect the imported source details. A successful original decode can use the sensor data. If that decode fails, the app may use a usable embedded preview as a clearly marked fallback. It marks the source and keeps an orange warning through export and cache restore.
A fallback preview has its own dimensions and bit depth. Exporting it to Float32 DNG or TIFF16 does not restore the camera's full sensor resolution, Bayer samples, or precision. If no usable preview exists, the original failure remains.
Read the format comparison for sharing and delivery options, or the RAW versus preview guide to check what imported.
Keep an editable route back
Export a shareable JPEG or PNG separately from the master you plan to edit. Preserve the original captures and recipe so a later change to alignment, crop, or projection does not depend on a flattened panorama.
For a different desktop workflow, see the Microsoft ICE alternative guide. Float32 output protects values present in the stitched working image; it is not a substitute for keeping the inputs.