Deliver the result. Keep what you need to pick it back up.

Write the delivery criteria

Before you deliver, note where the file is headed: editing, compositing, print, web or social media. Set the dimensions, aspect ratio, frame rate, duration and whether there's an alpha channel. Also ask about the expected color space, naming and size constraints. A label like "high-quality video" doesn't specify what the recipient will be able to modify or what their software will be able to open.

Prepare three sets: the approved delivery, the reusable intermediate assets and the archive of the work. They may share some resources, but each folder should state its role. Add a reference image or short video that shows the expected look.

Choose the format based on the next step

For an image meant for display, PNG can work for a display image with possible transparency; its dimensions, depth and color are still up to you. JPEG can serve for a lightweight check when some loss of quality is acceptable. To bring a render into a compositing or grading tool, OpenEXR preserves floating-point data and can carry multiple channels. The choice depends on the intended processing, not just the studio's preferred extension.

Don't confuse 16-bit integer and 16-bit float: they don't represent values the same way. Also check that the receiving application reads the layers and compression you chose. A small export opened in that tool before the full render is more useful than a theoretical list of supported formats.

Keep the useful passes, not all of them by reflex

Decide on the retouches that are actually needed before rendering: isolate a product, adjust a background or rework a light contribution. Enable the useful passes and verify they're present in a small file opened by the recipient. A list of layers visible in Blender doesn't prove they were saved in the delivered export.

Avoid piling up every channel out of habit: each element should have a use and someone able to review it. The guide Preparing compositing passes covers the detailed choices. Here, receiving means comparing the agreed channels against the ones present, then performing a simple retouch on the test image. Keep its settings with the inventory.

Control Color and Outlines

Keep the display transform, exposure and color choices used in the spec sheet. A file meant for compositing and a display-ready image shouldn't be imported blindly with the same settings. Open a reference in both applications and resolve the discrepancy before sending a long sequence. The guide Consistent colors details this check.

For a keyed image, examine the edges on a light background then a dark one at delivery size. Specify the alpha interpretation the recipient expects. A halo can come from the import, not from the render's sample count. The guide Alpha and compositing helps isolate this problem. Your final spec sheet keeps the decision made, without asking the recipient to guess it.

Exporting an animation frame by frame before encoding

A numbered sequence lets you redo missing frames without recalculating the whole film. It also keeps a step separate from video encoding. Choose the format of these images based on the remaining work, then assemble a review version at the right frame rate. The final video file must come from the approved sequence, not from an old series still sitting in the folder.

Check the start, the end and the frame count, then watch the sequence at normal speed. Inspect the shot changes, flickering and any jumps. A multilayer EXR sequence may require a compositing pass before editing; don't force a format on the recipient that their pipeline can't handle.

The guide to frame rates and sequences spells out the boundaries and playback. Don't treat one image that opens as validation of all the others: also check the inventory of the full range.

Hypothetical example: a product shot and its re-render

Let's imagine a six-second shot at 24 frames per second, or 144 frames. The client wants a validation video and the compositing team still needs to adjust the background. In this hypothetical example, the delivery includes the review video identified as v05, an EXR sequence with the agreed passes and a sheet specifying the frame rate, the display transform and the range 1001 to 1144.

The archive contains the corresponding .blend file, its textures, the versions and the retouch notes. A JPEG image of the approved render accompanies the sheet, without replacing the EXRs. Before sending, the team imports three images and checks the product mask. This example describes a delivery check; it is neither a measured result nor a time estimate.

Archiving the recipe for a generated image

For a ComfyUI result, keep the workflow JSON with node versions, the models used, the parameters and the seed. A media file's metadata can contain the workflow depending on the save node and the options used, but a conversion or a sharing platform can strip it. So keep the JSON file separately and check that it reloads.

Attach the necessary inputs when their rights allow them to be transmitted. Document models by their exact name, version and provenance rather than automatically redistributing all weights. A seed alone does not explain an image: the parameters, dependencies and output processing matter too. The archive should make the method understandable, without promising a perfect match between environments.

The Céramique manifest illustrates this separation between recipe and weights. The transmission rights for your own assets still need to be verified.

Examine file information without confusing it with quality

If FFmpeg is available on your machine, the command below offers a readout of the video file's information without modifying it. It was not run for your delivery. Replace the name with your file's name and keep the report alongside the export. The dimensions and frame rate information can help spot a bad preset.

This data proves neither the accuracy of the colors nor the continuity of motion. An average frame rate alone does not explain a variable frame rate file. Also watch the entire video, with its audio if any. A disagreement between the report, the delivery log and the viewing calls for a check before sending.

ffprobe -v error -show_entries stream=codec_type,codec_name,width,height,avg_frame_rate:format=duration -of json "livraison_v05.mp4"

Do the intake check before closing the project

Open the exported files from their final location. Check dimensions, frame rate, any audio, transparency and version name. For a sequence, look for missing numbers and empty files. Compare the transferred volume and, if your copy method allows it, the checksums. Do not treat a completed transfer as proof that the frames are usable.

The final deliverable is an explicit set: approved files, a short readme sheet, authorized sources and an inventory of dependencies. Keep an independent copy before freeing up your workspace. The video workshop helps prepare edit versions; the 3D workshop helps choose the passes.

Reject false signs of completion

A large folder can contain an old version; a playable video can come from the wrong sequence; identical fingerprints can confirm the copy of a file that was already incorrect. So cross-check three things: the right set of files, an intact copy and acceptable content. They answer different questions.

You can start from a copy of the Pli receipt form. Fill in the real observations and reservations. Pli provides no validated Blender render: the form is a support for your check. The RenderParcel notebook keeps notes; backing up scenes, models and exports still needs to be organized on an independent medium.