Draft is a tool that provides simple and lightweight compositing and video processing functionality, designed to automate typical post-render tasks. It is implemented as a Python library (works across all platforms), which exposes functionality for use in Python scripts (which are referred to as Draft Templates). Draft is designed to be tightly integrated with Deadline, but it can also be used as a Standalone tool.

Please note, new Quick Draft options have been added to most of the job submitters that allow you to easily create movies from your rendered images or perform file conversions, without having to create a Draft template (Python) script. Instead, a generic Draft template that ships with Deadline is now used, and it lets you specify settings like Output Type, Codec, Resolution, and Frame Rate. See the Draft Event plugin for more information.

Many Draft code snippets from our Draft Cookbook can be found in our Draft Documentation.

Draft Repository Paths:

  • Sample Draft Scripts: /<DeadlineRepository>/draft/Samples
  • Draft OCIO/ACES LUTs: /<DeadlineRepository>/draft/ocio-configs
  • Draft for Linux: /<DeadlineRepository>/draft/Linux
  • Draft for Mac: /<DeadlineRepository>/draft/Mac
  • Draft for Windows: /<DeadlineRepository>/draft/Windows


Draft and Quick Draft are both licensed by the same, additional FlexLM FEATURE draft in your Thinkbox license file. Draft/Quick Draft is free for users with an active Deadline annual support and maintenance contract. Ensure when updating your Deadline license file you also update your version of Draft where applicable. The majority of Draft features require ONLY that a license be present. Actual checkout of licenses happens ONLY while videos are being encoded or decoded. Draft/Quick Draft (incl. Draft Tile Assembler - Jigsaw) will NOT work whilst in LICENSE-FREE Mode or your Deadline annual support contract has expired.


While the Deadline repository installer ships with a build of Draft, via our beta program or otherwise, it is possible a newer version of Draft might be available via our beta forums. Draft builds are regularly released independently of Deadline. Draft can be upgraded independently of Deadline. Once you have downloaded the latest Draft build, simply extract the .zip file into your repository only under the Draft folder. The slaves will automatically sync up new versions of Draft to their local working folders when needed, similar to Deadline’s regular auto-update system. You can verify your version of Draft in a Python script like this:

import Draft
print Draft.LibraryInfo.Version()

Job Submission

There are many ways to submit Draft jobs to Deadline. As always, you can simply submit a Draft job from within the Monitor from the Submit menu. In addition, we’ve also added a right-click job script to the Monitor, which will allow you to submit a Draft job based on an existing job. This will pull over output information from the original job, and fill in Draft parameters automatically where possible.


On top of the Monitor scripts, you can also get set up to submit Draft jobs directly from Shotgun. This will again pull over as much information as possible, this time from the Shotgun database, in order to pre-fill several of the Draft parameter fields. See the Integrated Submission Script Setup section below for more details on this.

We’ve also added a Draft section to all of our other submitters. Submitting a Draft job from any of these uses our Draft Event Plug-in to submit a Draft job based on the job currently being submitted (this is similar in concept to the right-click job script described above). The Draft job will get automatically created upon completion of the original job via the OnJobFinishedCallback in the Draft event plugin.

Submission Options

The general Deadline options are available in the Draft submitters, and are explained in the Job Submission documentation. Draft-specific options are explained below. It should be noted, however, that given the nature of Draft scripts, not all of these parameters will be used by all scripts. They can even feasibly be used for different purposes than listed here.

Draft Options

  • Input File: The input file(s) on which to apply the Draft script. Passed to the Draft script as ‘inFile’.
  • Output Folder Name: The output folder in which the Draft script should put output files. Can be absolute, or relative to input folder. This is passed to the Draft script as ‘outFolder’.
  • Output File Name: The name that the script should use for the output file(s). Passed to the Draft script as ‘outFile’.
  • Frame List: The list of Frames that should be processed by the script. Passed to the Draft Script as ‘frameList’, ‘firstFrame’, and ‘lastFrame’.
  • Distributed Job: Specify if the job will be distributed. If enabled, custom scripts must work with taskStartFrame and taskEndFrame.
  • Frames Per Task: The number of frames, or chunk size, to be assigned to each task.
  • Machine Limit: The maximum number of machines that can process a distributed job at one time. Specify 0 for no limit.

Quick Draft Options

If selected, Draft will generate an image or a movie based on the options specified below.

  • Format: The output format used by the Quick Draft submission.
  • Compression: The compression used by the Quick Draft submission.
  • Resolution: The resolution used by the Quick Draft submission.
  • Quality: The quality used by the Quick Draft submission.
  • Frame Rate: The frame rate used by the Quick Draft submission.

Custom Draft Options

If selected, Draft will generate a job using the Draft template specified below.

  • Draft Template: This is the Draft script (or Template) that you want to use.
  • User Name: The user name used by the Draft template. Typically used by the Draft script for frame annotations. Passed to the Draft script as ‘username’.
  • Entity Name: The entity name used by the Draft template. Typically used by the Draft script for frame annotations. Passed to the Draft script as ‘entity’.
  • Version Name: The version name used by the Draft template. Typically used by the Draft script for frame annotations. Passed to the Draft script as ‘version’.
  • Additional Args: Any additional command line arguments that you wish to pass to the Draft script should be listed here. Appended to arguments listed above.

Plug-in Configuration

The Draft plug-in requires configuration only if choosing not to preserve the render environment while running as a specific user on Unix systems. For details, see Perserving Specific Environment Variables with Sudo.

Integrated Submission Script Setup

All of our integrated submission scripts have been updated to have a Draft section, in order to submit dependent Draft jobs. In addition to this, we also have created scripts to allow you to submit a Draft job directly from Shotgun.

Shotgun Action Menu Item

The best way to install the Draft Submission menu item in Shotgun is to use the automated setup script included in the Monitor. To access this, select Scripts -> Install Integration Submission Scripts from the Monitor’s menu. From there, click the ‘Install’ button next to the Draft entry.

It should be noted that this functionality is currently only available on the Windows version, and requires administrator privileges to run successfully. It should also be noted that while this script will create the ‘Submit Draft Job’ entry in Shotgun for everyone to see, this must still be done on each machine that will be submitting Draft jobs.

Draft Standalone

Draft can be used outside of Deadline (it still requires a draft license). In order to import Draft successfully, you will need to ensure Python knows where to look for the Draft module, either by including its install directory in the PYTHONPATH environment variable, or by appending it to os.sys.path before you do the import. You will also need to set the MAGICK_CONFIGURE_PATH and LD_LIBRARY_PATH (or DYLD_LIBRARY_PATH) environment variables to point to your install directory; this is so that ImageMagick knows where to find its ‘type.xml’ file. If you are simply planning on using Draft through Deadline, however, you do not need to worry about this at all.

If using Deadline’s Python, ensure you use these paths to instantiate dpython as they ensure the Deadline environment is setup correctly:

  • Windows: C:\Program Files\Thinkbox\DeadlineX\bin\dpython.exe
  • Mac OS X: /Applications/Thinkbox/DeadlineX/Resources/dpython
  • Linux: /opt/Thinkbox/DeadlineX/bin/dpython

where X is the MAJOR version of Deadline.

All platforms need specific environment variables to be set for Draft Standalone (Python) to successfully import Draft:

  • Windows:

    PYTHONPATH=/path/to/Draft install directory/Windows/XXbit
    MAGICK_CONFIGURE_PATH=/path/to/Draft install directory/Windows/XXbit
    where XX is either 32 or 64.
  • Mac OS X:

    PYTHONPATH=/path/to/Draft install directory/Mac
    MAGICK_CONFIGURE_PATH=/path/to/Draft install directory/Mac
    DYLD_LIBRARY_PATH=/path/to/Draft install directory/Mac
  • Linux:

    PYTHONPATH=/path/to/Draft install directory/Linux/64bit
    MAGICK_CONFIGURE_PATH=/path/to/Draft install directory/Linux/64bit
    LD_LIBRARY_PATH=/path/to/Draft install directory/Linux/64bit


Does Draft/Quick Draft need a license to run?

Partially. See the Licensing section for an explanation.

Can I upgrade Deadline without upgrading the version of Draft I’m using?

Yes. See the Upgrading or Downgrading Draft section of the Upgrading or Downgrading Deadline documentation for more information.

Why does my custom Deadline 7 Draft submitter code no longer work in Deadline 8.0 or later?

Please note that as of Deadline 8.0, when submitting Draft jobs to Deadline, the KEY=VALUE entry for the Draft Plugin is named as follows in the job info file:


Error Messages and Meanings

This is a collection of known Draft error messages and their meanings, as well as possible solutions. We want to keep this list as up to date as possible, so if you run into an error message that isn’t listed here, please email Deadline Support and let us know.

Currently, no error messages have been reported for this plug-in.