Your Mac Can Finally Make DCP Delivery Drives – INT DCP Baker Costs Just $20

Software News

by Nino LeitnerAugust 17^th, 2026

Subscribe to News - Software

Getting a finished DCP onto a drive that a cinema server will actually accept still tends to involve a Linux machine, a virtual machine, or a paid file system driver. A small Tokyo software house now claims the entire job can be done inside a single macOS window, for the price of two coffees. INT DCP Baker v1.0 builds EXT3 and EXT2 delivery media on Apple silicon Macs, verifies what it wrote, and leans on a piece of Apple software most filmmakers have never heard of.

Interceptor Inc., a Meguro, Japan-based developer that also runs a video production studio, has released INT DCP Baker v1.0, a macOS application that turns an existing Digital Cinema Package into delivery media without leaving the Mac. It requires an Apple silicon machine running macOS 26.0 or later, and splits the process into two stages the developer calls PREP and BAKE: disk image creation first, then writing to the external medium and verifying the result. EXT3 is the recommended target format, with EXT2 also supported, several DCPs can be placed on a single medium, and a previously created image can be reused across multiple drives. The interface is available in Japanese and English, a seven-day trial runs with all features enabled, and the full license is a one-time purchase at USD 20.

Why a DCP is not just a folder you copy

Anyone who has delivered to a theatrical venue knows the problem this addresses. Digital cinema servers run Linux, and the file system that reliably survives ingest across Doremi, Dolby, GDC, and Barco hardware is EXT2 or EXT3, not the APFS or exFAT volumes a Mac produces by default. Copying a DCP folder onto a general-purpose USB drive frequently produces media the venue cannot read at all, and the partition structure matters as much as the file system itself, since many servers expect an MBR layout rather than the GUID scheme macOS writes without being asked.

That gap sits at an awkward point in the post workflow. The DCP itself is the easy part in 2026: DaVinci Resolve Studio authors packages on the Deliver page, and DCP-o-matic does the same for free, but neither of those steps formats a drive the way a projection booth expects. Historically, closing that last gap has meant keeping an Ubuntu machine around, running a Linux VM, buying a commercial EXT driver for macOS, or handing the job to a facility. For a one-off festival delivery, all of those feel disproportionate.

What actually happens during PREP and BAKE

During PREP, the user points the application at a working folder, the DCP material, and the destination medium. INT DCP Baker then builds a disk image with the structure commonly required for DCP delivery, which according to Interceptor means an MBR partition scheme, Linux partition type 0x83, an inode size of 128 bytes, and reserved blocks set to 0%. That last detail is worth pausing on, because Linux normally reserves 5% of a volume for root, space that is simply wasted on a delivery drive and can push a large package over capacity.

BAKE writes the completed image to the external medium as RAW data, then reads the medium back and compares the resulting SHA hash against the hash of the source image. The application outputs a Bake Report containing those verification results, which is exactly the kind of artifact you want to attach to a delivery email when a venue later claims the drive was faulty. Image sizing can follow either the size of the DCP or the capacity of the destination medium, and separating the two stages means the image contents can be checked before anything is written, then reused for a second, third, or tenth copy of the same show.

Apple’s container tool doing genuinely unglamorous work

The interesting technical detail is where the EXT file system comes from. INT DCP Baker uses Apple’s container tool, the Swift-based utility built on the Containerization framework that Apple open-sourced at WWDC 2025 and shipped as version 1.0.0 in June 2026 under an Apache 2.0 license. It runs Linux containers as lightweight virtual machines on Apple silicon, one VM per container, and the underlying Containerization package includes the ability to create and populate EXT file systems. Interceptor is effectively borrowing a developer tool aimed at people building server software and pointing it at a delivery problem.

The practical consequence is that no separate Docker Desktop installation, no manually maintained Ubuntu VM, and no third-party kernel extension is involved. It also explains the hard system requirement: Apple’s container tool is supported on macOS 26 and Apple silicon only, so anyone still working on an Intel Mac, or holding back an OS upgrade for plugin compatibility reasons, is out of scope. Given that Apple’s current hardware lineup has been Apple silicon only for years, that will not affect many working post rooms, but it is worth checking before paying.

Validation, and what the application deliberately does not do

Interceptor states that media created with INT DCP Baker have been mounted as an EXT3 volume on Ubuntu, passed the DCP-o-matic Validator, been successfully ingested by a Doremi DCP-2000, and matched the source SHA hash during the application’s own post-write Readback. That is a more specific validation claim than most software announcements in this corner of the industry offer, and the Doremi ingest in particular is the test that counts. It is also, by definition, the developer’s own testing rather than independently verified results, and one server model is a narrow sample given how much venue-to-venue variation exists in the field. Nobody should skip a test screening on the strength of a spec sheet.

The company is refreshingly clear about the boundaries. INT DCP Baker does not add general EXT3 and EXT2 read and write support to macOS, so it will not help you open a returned delivery drive to check its contents. It does not create or convert DCP content either; the package has to exist already, whether it came out of Resolve, DCP-o-matic, or a facility. Because the workflow routes through an intermediate disk image, working storage is required on top of the DCP data itself, and time has to be budgeted for image creation, the write, and the verification pass. For a feature-length package on a slow USB drive, that is not a five-minute errand.

Where twenty dollars sits against the alternatives

The obvious comparison is DCP-o-matic’s Disk Writer, which is free, cross-platform, and writes EXT2 volumes, and which many independent filmmakers already use. Commercial EXT drivers for macOS exist as well, though they solve a broader mounting problem at a higher price. What INT DCP Baker adds to that picture is the combination of EXT3 as the default target, MBR and inode parameters set for cinema servers rather than general Linux use, multi-DCP media, reusable images, and a written verification report, all in one interface at a price low enough that it does not need a business case.

Whether that is worth paying for depends entirely on how often you deliver. If a theatrical drive leaves your studio twice a year, the free route plus patience is perfectly reasonable. If you are a boutique post house pushing festival and distributor deliveries out regularly, an audit trail and a workflow that does not require booting a second machine has obvious value, and the reusable image alone could pay for itself the first time a distributor asks for five identical drives.

INT DCP Baker v1.0 costs USD 20 as a one-time purchase, with a seven-day trial that enables all features. It requires an Apple silicon Mac running macOS 26.0 or later, supports EXT3 and EXT2, and ships with Japanese and English interfaces. Full details, purchase links, and the user guide are available on the Interceptor Inc. product page, with the English user guide published separately.

How do you currently get your DCPs onto delivery media, and would a verified one-click bake on the Mac change that routine? Don’t hesitate to let us know in the comments below!