Is it free?
It is free to download during the alpha. You need a free alpha licence: request one here.
Is it ready for production?
Not yet. This is an alpha: expect bugs, missing pieces and the odd crash. Test it on real shots next to your current pipeline, and keep delivering with what you trust.
When is the beta?
There is no date to announce. The beta comes when clean installs work everywhere, the Nuke shortcut list is complete and the app has no stalls in everyday work.
Is it open source?
No. Oink is proprietary software by MegaSuperSoft. It includes open-source components (FFmpeg, OpenImageIO, OpenColorIO, Cycles, Electron and others); their licences and source are listed with every download.
Can I open my Nuke scripts?
Yes. .nk scripts open: nodes, knobs, expressions, groups and links are translated, and anything that cannot be is listed. You can also export back to .nk and copy and paste between the two.
How is .oink different from .nk?
.oink is Oink's own comp file: plain JSON text, so it diffs and merges cleanly in version control. .nk stays a first-class import and export format.
Do gizmos and OFX plugins work?
Gizmos load from ~/.nuke, ~/.opencomp/gizmos or NUKE_PATH and show in the Tab menu. OFX plugins run in a separate process, so a crashing plugin does not take your session with it.
Does it do deep compositing?
Yes, with 9 deep nodes: DeepRead, DeepToImage, DeepMerge, DeepHoldout, DeepTransform, DeepCrop, DeepRecolor, DeepFromImage, DeepReformat.
Which Python?
Python 3.13, bundled with the app. import nuke gives you 309 functions of Nuke's Python API, enough for most pipeline tools and menus.
Which graphics card do I need?
Any GPU with OpenGL 4.6 on Linux, or DX12 / Metal on Windows and macOS, runs the compositor. GPU Cycles and the AI tools are built for NVIDIA cards.
Will it run on a laptop without NVIDIA?
The compositor will. The AI tools and Cycles fall back to the CPU, which is much slower, and the largest AI models need more graphics memory than most laptops have.
Does it run on Intel Macs?
No. The macOS build is for Apple Silicon and needs macOS 14 or newer.
Which Linux distributions?
x86-64 with glibc 2.34 or newer. It is tested on Rocky Linux 9; other current distributions should work but are not tested yet.
Is Cycles available on Mac and Windows?
Not yet. Cycles and USD rendering ship in the Linux build today; macOS and Windows get them later.
Do I need Blender?
No. Blender 5.2 LTS is optional and only adds EEVEE renders and opening .blend files.
Can I use our studio's OCIO config?
Yes. Point $OCIO at your config, as you would for Nuke; without it, Oink uses its bundled config.
What leaves my machine?
Alpha and beta builds send crash reports and anonymous usage counts: never footage, file paths, comp or shot names. You can turn this off in the app; stable releases have it off. Otherwise the network is used only for things you start: licence check-ins, updates, model downloads and bug reports.
Can a studio run it offline?
Yes. A policy file with "offline": true blocks every internet request, usage reports included. The alpha licence needs a check-in at least every 14 days.
How many machines can I use?
An alpha licence covers two machines, for example a workstation and a laptop.
How do updates work?
The app checks a signed release list and asks before installing (studios can switch this off or make it automatic). Pick the stable, beta or alpha channel; Help > Check for Updates... checks right away.
How do I report a bug?
Help > Report a Bug... writes an email to support@megasupersoft.com with a diagnostic bundle you can read first. File paths, names and tokens are removed from the bundle before you see it.
Where are the logs?
~/.cache/opencomp/logs on Linux, ~/Library/Logs/opencomp on macOS, %LOCALAPPDATA%\opencomp\logs on Windows. Help > Open Log Folder takes you there.
How do I uninstall it?
Windows: Settings > Apps or the Uninstall entry in the Start menu. macOS: drag the app to the Trash. Linux: run ./uninstall.sh in the installed folder. Your settings and caches are kept unless you delete them.
Why does Windows or macOS warn about it?
Alpha builds are not code-signed yet, so the system warns once. The first-launch steps in Downloads get past it.