For Windows creators / Experimental Resolve script

Windows Resolve
Script Beta.

On Windows? Start here. A lightweight queue that runs inside DaVinci Resolve Studio, not as a standalone Windows app. Try it with copied test clips and help us improve the Windows workflow. Secondary macOS and Linux downloads are also available below.

Free public beta0.2.0-beta.9September 9, 2026

Join the Windows beta tester list

H.265 · 10-bit 4:2:2All-Intra · independent framesProRes · available profiles

H.265 and All-Intra unlock separately after a full selected-clip test in Settings. Approval lasts for the current panel session.

Start here for Windows

Windows

Live Windows testing pending

Download Windows ZIP
Free download requested

Before you try the beta.

This is Resolve Script Beta, not a standalone Windows app or the stable Mac app. It requires Resolve Studio 21.1+, Python 3, FFmpeg and ffprobe. Extract both folders and follow the setup guide.

H.265 10-bit 4:2:2 and All-Intra require separate full-clip tests in Settings before use. Windows/Linux hardware remains unverified. Experimental N-RAW choices do not establish full Mac camera-color equivalence. Allow enough cache space, use copies and review the result.

Help us improve it: optional private diagnostics are off by default and can be enabled in the script settings. No email or media is sent.
Read setup guide

On Windows? Start here.
Runs inside DaVinci Resolve Studio, not as a standalone Windows app.

Portable Python script, about 47 KB. Dependencies are separate.
Other platforms

macOS

Selected R3D / HEVC / ProRes tests passed

Download macOS ZIP
Free download requested

Before you try the beta.

This is Resolve Script Beta, not a standalone Windows app or the stable Mac app. It requires Resolve Studio 21.1+, Python 3, FFmpeg and ffprobe. Extract both folders and follow the setup guide.

H.265 10-bit 4:2:2 and All-Intra require separate full-clip tests in Settings before use. Windows/Linux hardware remains unverified. Experimental N-RAW choices do not establish full Mac camera-color equivalence. Allow enough cache space, use copies and review the result.

Help us improve it: optional private diagnostics are off by default and can be enabled in the script settings. No email or media is sent.
Read setup guide
Portable Python script, about 47 KB. Dependencies are separate.
Other platforms

Linux

Live Linux testing pending

Download Linux ZIP
Free download requested

Before you try the beta.

This is Resolve Script Beta, not a standalone Windows app or the stable Mac app. It requires Resolve Studio 21.1+, Python 3, FFmpeg and ffprobe. Extract both folders and follow the setup guide.

H.265 10-bit 4:2:2 and All-Intra require separate full-clip tests in Settings before use. Windows/Linux hardware remains unverified. Experimental N-RAW choices do not establish full Mac camera-color equivalence. Allow enough cache space, use copies and review the result.

Help us improve it: optional private diagnostics are off by default and can be enabled in the script settings. No email or media is sent.
Read setup guide
Portable Python script, about 47 KB. Dependencies are separate.

What you can explore

A queue you control

Add individual clips, reorder or remove them. Save per-clip formats and custom H.265 limits from 25 to 800 Mb/s with your queue.

Keep track of exports

See clearer verification status, elapsed time and approximate ETA. Review output size, measured bitrate and PNG previews saved beside exports.

Watch folders and timelines

Try watched-folder queues with a five-second cancellation window, or retain a prepared N-RAW timeline for later. Keep the entire Timeline Builder output folder. The panel must remain open for listening.

Test your encoder first

Enable H.265 Lower, Standard and Higher after a passing test. All-Intra has its own test. Unsupported modes stop clearly; there is no silent 8-bit or 4:2:0 fallback.

Know what finished

Exports are checked for format, dimensions, frame rate, timecode and original audio. All-Intra is also checked for independent frames. Estimated targets are not guaranteed file bitrates.

Stay in control

Pause between clips, retry unfinished work, relink moved media and choose a cache folder. Existing exports are protected. Automatic diagnostics and beta updates are separate opt-ins.

Your first export

Test once. Then queue.

  1. Select a short copied clip and a new output folder.

    Compatibility tests render the entire selected clip, so leave enough time and disk space.

  2. Open Settings and test the mode you need.

    Choose Test H.265 on selected clip for Lower / Standard / Higher. Choose Test All-I on selected clip separately for All-Intra. A failed test leaves that mode unavailable.

  3. Review the image, then choose per-clip outputs.

    Check exposure, color, detail and audio yourself. A technical pass cannot judge the look. Use available ProRes options if that better fits your workflow.

  4. Keep the panel open while it works.

    Watch folders and session-specific compatibility approvals belong to this open panel. Reopening the script requires new H.265 / All-I tests. Each later export is still verified.

Which output should I choose?

Standard H.265 prioritizes compact files. Higher raises the target; Lower reduces it. All-Intra uses independent frames and a substantially higher target, so files are usually larger. Available ProRes profiles prioritize editing workflows rather than the smallest archive.

Preset targets adapt to frame rate. Custom H.265 limits of 25 to 800 Mb/s can be set per clip and saved with the queue. Actual bitrate depends on content and encoder behavior, not just the requested limit. None of these exports retain adjustable camera-RAW controls.

Using the experimental N-RAW options

Choose native Nikon N-Log or the experimental NEV-as-R3D option. Both need enough cache space for a full-size private copy. Original footage stays untouched. Review colors and exposure yourself; full IPP2 and Mac image equivalence are not proven. Retained Timeline Builder projects need their entire output folder kept in place.

Start with a short test

Install inside Resolve.

Open the illustrated beta User Guide for ten clickable sections and an offline PDF.

  1. Check requirements.

    DaVinci Resolve Studio 21.1 or later, a working Python 3 environment recognized by Resolve, and FFmpeg plus ffprobe available in PATH or selected in the script settings. Your OS, GPU and codec must also be supported by Resolve. This download does not install Resolve, drivers or system dependencies.

  2. Extract both folders from the ZIP.

    Place Scripts and ZR RAW Script Beta together inside your user Fusion folder. Merge Scripts without replacing unrelated scripts. Do not put the runtime folder inside Scripts.

    Windows installation location%APPDATA%\Blackmagic Design\DaVinci Resolve\Support\Fusion
    macOS installation location~/Library/Application Support/Blackmagic Design/DaVinci Resolve/Fusion
    Linux installation location~/.local/share/DaVinciResolve/Fusion
  3. Open the script.

    Restart Resolve if needed, then use Workspace > Scripts > ZR RAW Script Beta (under Utility on some installations). Read BETA_START_HERE.md from the extracted runtime folder if the entry is missing.

  4. Try a copy, review the result.

    Save your current Resolve work. Use a test project library, copied media and a new output folder. Check image, audio, timing and framing before trusting a longer queue. The beta does not replace your native Mac app.

Feedback without an inbox full of email

Help improve the beta.

Optional diagnostics are off by default. Enable them in the script settings to share a small, structured success or failure report privately with the developer. Exports do not depend on submitting a report.

What is shared, and how to delete it

Reports contain the beta build, broad OS and architecture, Resolve version, input category, outcome and a predefined error category. They do not include your name, email, media, file paths, project names or full logs. Each report has its own random case ID, not a persistent device ID.

Reports are stored separately from Mac support on Cloudflare and removed by scheduled cleanup after 30 days. The server uses a short-lived hashed IP value to limit abuse; the application does not store raw IP addresses. Cloudflare still processes network requests, and its infrastructure retention is separate.

Turning diagnostics off clears pending local reports. Use the script's sent-report deletion option to remove reports for which it saved a receipt. Known limitation: if the first submission response is lost, its deletion receipt cannot be recovered; retries may remain queued for up to seven days and delay later reports. The server copy still expires through retention cleanup.

This is anonymous diagnostic feedback, not a two-way support chat. No email is sent and the developer cannot contact you from a report.

For suggestions or a description of your experience, join the YouTube discussion. Comments there are public, so never post private paths, credentials or personal footage.

What's tested, and what is still experimental?

On macOS Resolve Studio 21.1, genuine 6K and 4K N-RAW exports passed native dimensions, frame rate, frame count, full decoding, camera timecode and sample-identical original 32-bit float audio. Every frame of the 204-frame All-Intra test was independently encoded. A retained builder project reopened with its media online, and short listener cancellation, restart and automatic-export tests passed. Prior Beta 8 selected R3D H.265, All-Intra and ProRes evidence remains separate.

Windows/Linux live rendering, installation and visual consistency remain unqualified. Full Mac pixel/color/IPP2 equivalence, ProRes RAW, temporal noise reduction, direct Camera RAW editing and grade preview are not established or not included. PNG previews are saved beside exports, not displayed inline. Long unattended listener and recovery stress tests remain pending. No universal GPU, image-quality or bitrate guarantee is implied.

Updating an existing script installation

Optional beta update checks are off by default. Beta updates use their own channel, separate from the native Mac app. Close and reopen the script to activate a staged update, never during an export. Current beta.5 through beta.8 bootstrap installations can receive this runtime update; older launcher installations may need manual setup using the complete ZIP. Initial downloads rely on HTTPS and the published checksum; runtime updates are signature-checked.

Dated beta releases

What's new in Beta 9

September 9, 2026 · 0.2.0-beta.9

Full release notes and limits · Download checksums

Older beta releases

Beta 8 · September 9, 2026. Added independently tested H.265 10-bit 4:2:2 and All-Intra options.

Beta 8 notes · Windows beta.8 ZIP

Beta 7 · September 9, 2026. Initial public ProRes-focused script.

Beta 7 notes · Windows beta.7 ZIP