
Do not use OpenToonz Save Previewed Frames as proof of a higher-bit-depth final delivery. The 1.7.1 manual says saved preview frames always have 8-bit color depth, regardless of the Output Settings or Preview Settings depth choice. Render a fresh output through the final rendering route when delivery requires supported 16-bit channels.
Key Takeaways
- A preview save and a final render are different output paths.
- Choosing a high-depth setting does not change the preview-save limit.
- Check the actual file's depth, dimensions and frame range.
Identify which command produced the file
The official rendering guide documents Save Images in the Viewer and Save Previewed Frames in its context menu. Although the saved format and its options use Output Settings, a separate note fixes the saved preview depth at 8 bit.
Keep the existing file as a labeled review copy. Record whether it came from that preview route or Render > Render. A TIFF extension or a 16-bit dialog setting alone does not establish the stored file's channel depth.
Configure a compatible final output
In Output Settings, choose the required Channel Width and a format that supports it. The manual gives TIF with 64(RGBA) as an example supporting 16-bit channels. Treat the recipient's format requirement as the deciding contract rather than assuming every available format preserves the same depth.
Check the final camera resolution and frame range as well. Preview settings can include Shrink, Step and different camera choices; those review conveniences should not silently become the delivery specification.
Use Render > Render to produce the chosen final output at a separate destination. Keep the preview copy and final output clearly named.
Proposed example: a gradient for later compositing
Suppose a soft background gradient is supplied for further color work and the compositor asks for 16-bit channels. A saved preview looks acceptable but is not the required depth. Render a compatible final sequence, then inspect a representative file with a viewer or file-information tool that reports channel depth.
Compare its visible gradient with the approved reference and confirm resolution and alpha if required. This proposed check does not claim that higher depth removes banding already present in an 8-bit source.
Accept the stored data and the intended appearance
Verify the first and last requested frames and representative images between them. Record the format, per-channel depth and dimensions from the delivered files.
If a file still reports 8 bit, retrace the output route and compatible format options before increasing quality elsewhere. The task is complete when the actual output meets the agreed data requirements and looks correct, not when the editor displays a higher-depth setting.
Related tasks
- Captions look correct in preview but move in the export: isolate a small render test
- Why Does Media Encoder Render Again After I Rendered Premiere Previews?
- Why Did My Layered PSD Arrive Flattened in Final Cut Pro?
Sources and scope
- OpenToonz1.7.1 official documentation: Saved preview frames always use8-bit depth despite Output or Preview depth options.
Documentation-based synthesis of the OpenToonz 1.7.1 published manual and saved official full-body captures read on 2026-10-23. Later software releases may differ. Examples are proposed checks, not executed tests. No measured search volume or AI citation frequency.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: Paparazzi Ratzfatzzi / Pexels, Pexels License. This is an illustrative source photograph, not an application screenshot or a generated test result.