Skip to content
Tensor
FeaturesInstallPricingFAQ
Sign inCreate account
ENFR
FeaturesInstallPricingFAQSign in
Create account

Install guide

Tensor 0.1.0, released 16 November 2026. Everything here is checked against the package and the client of this release.

Contents
  1. Requirements
  2. Get Tensor
  3. Install with the installer
  4. Install from the ZIP
  5. Studio deployment
  6. First launch
  7. Offline use
  8. Render farms
  9. Updates and security advisories
  10. Problems

Requirements

  • Nuke 15, 16 or 17 (the 15.0, 16.0 and 17.0 lines), on Windows 10 or 11. Linux is coming later; macOS is not supported.
  • GPU: optional. TBlur, TMask and TNoise use an NVIDIA GPU with a current driver when there is one, and fall back to the CPU when there is none or when the GPU cannot do the job. TMask and TNoise give the same pixels on the CPU; TBlur gives the same image within a tiny tolerance (float precision). TColorRamp runs on the CPU. The plug-ins load on a machine without an NVIDIA driver.
  • A web browser on the machine, for the sign-in, and an internet connection for the first activation and for the licence renewal.
  • The path of your Windows user folder must be plain ASCII (no accented characters): Nuke itself cannot load plug-ins from other paths. With an accented user name, install into C:\Tensor (see the installer below).

Get Tensor

Sign in at account.tensorndk.com/download. If you have no account yet, create one there: the free 14-day trial is created automatically when you sign up, once your address is confirmed. Its 14 days start at your first activation in Nuke (see First launch below), not at the download. The trial is one per person: a verified email address (a +tag is ignored on any address, and the dots of a Gmail address count as nothing), a Google account and a computer. If any of the three already had a trial, a second one is refused (see the pricing rules and the FAQ).

The page offers two files for Windows, each with its size and its SHA-256:

  • Tensor-<version>-windows-setup.exe: the installer, recommended.
  • Tensor-<version>-windows-artist.zip: the same package as a ZIP, to unzip yourself.

These are the values of this release, 0.1.0 (16 November 2026). The same list is published for every release at updates.tensorndk.com/downloads.json:

File Size (bytes) SHA-256
Tensor-0.1.0-windows-setup.exe 3773371 62ddc17812ec376023035c28769988b149b1a607326424af5e5c2776b982cfcd
Tensor-0.1.0-windows-artist.zip 21726752 56fe7c4013d2f27ae6bb1f906254b9269e0c73342624c91f499fadc11cfdaf5d

Both carry the same Tensor folder, which holds Nuke 15, 16 and 17 (Tensor loads the plug-ins of the Nuke you start). Check the file before you run it, in the folder of the file:

certutil -hashfile Tensor-0.1.0-windows-setup.exe SHA256

Use the name of the file you downloaded. The hash printed must be the one above (or on the download page), letter for letter. It shows that the file is the one the page lists and that the download is not damaged; it is not a code signature. If it differs, download the file again.

Install with the installer

  1. Close Nuke. The installer asks you to when it finds Nuke running.
  2. Run Tensor-<version>-windows-setup.exe. The installer is not code-signed yet (this is a beta), so Windows SmartScreen may say unknown publisher: choose More info, then Run anyway.
  3. Follow the wizard (English or French, after the language of Windows). It installs for your user only: no administrator rights. By default it installs into %USERPROFILE%\.nuke\Tensor (you may pick another folder, whose last name is always Tensor) and adds a marked block, between the lines # >>> Tensor >>> and # <<< Tensor <<<, to .nuke\init.py, creating the file if it does not exist. A copy of an existing init.py is saved first as init.py.tensor-backup, and your own lines are never changed. If the HOME environment variable points to an existing folder, Nuke looks there first and so does the installer: your .nuke folder is then under HOME.
  4. Accented user name. The installer tells you at the start that Nuke cannot load plug-ins from such a profile. It then proposes C:\Tensor, touches no init.py, and its last page asks you to add that folder to the NUKE_PATH environment variable yourself (the installer does not edit your environment).
  5. Start Nuke and go to First launch below.

The installer contacts no server: it carries the whole package. The only network use is the sign-in in Nuke (see First launch).

Unattended install (many machines)

The installer is made with Inno Setup and takes its standard switches, so a studio can install the same way on ten machines without clicking through the wizard. Signed in as the Windows user who runs Nuke, in a Command Prompt:

Tensor-0.1.0-windows-setup.exe /VERYSILENT /SUPPRESSMSGBOXES /NORESTART /DIR="%USERPROFILE%\.nuke\Tensor" /LANG=english /IGNORENUKE=1 /LOG="%TEMP%\tensor-setup.log"
  • /VERYSILENT /SUPPRESSMSGBOXES: no wizard and no message box. The exit code says what happened.
  • /DIR=: the target folder. Its last name must be Tensor and the path must be plain ASCII (step 3 and step 4 above).
  • /LANG=english or /LANG=french.
  • /IGNORENUKE=1: go on while Nuke is running. Without it a silent install stops when Nuke runs (exit code 7) and changes nothing.
  • /LOG=: write the log there; it names the reason of any refusal. Read it whenever the exit code is not 0.
  • /NORESTART: never restart Windows.

Every refusal of the installer is exit code 7 with nothing changed, and the log says why: Nuke running, an accented profile without /DIR, or a folder that is neither an earlier Tensor install nor a real Tensor package. A silent install does exactly what the wizard does: the same Tensor folder, the same marked block in .nuke\init.py, no administrator rights, no restart, and nothing to answer. Each computer still needs its own sign-in in Nuke (see First launch), and that sign-in is a browser approval on that computer: it cannot be scripted or done from another machine.

To uninstall silently, close Nuke and run "%USERPROFILE%\.nuke\Tensor\unins000.exe" /VERYSILENT /IGNORENUKE=1 (a silent uninstall stops, exit code 1, while Nuke runs unless you pass /IGNORENUKE=1).

To uninstall with the wizard, use Windows Settings → Apps (Add or remove programs) and remove Tensor. The uninstaller removes what the installer put there and only its own block of init.py; your lines stay. Close Nuke first. Your licence (%ProgramData%\Tensor\license) and the update data (%LOCALAPPDATA%\Tensor) are left in place.

Install from the ZIP

  1. Close Nuke. Right-click Tensor-<version>-windows-artist.zip, choose Extract All, and type %USERPROFILE%\.nuke as the destination folder (your Nuke user folder; it is created if it is missing).

  2. You get a Tensor folder, tensor_loader.py and init.py. Nothing else to install, no administrator rights.

  3. If you already have an init.py there, do not replace it: choose Skip for init.py, and add this one line at the end of yours:

    import importlib.util; __import__("tensor_loader").add() if importlib.util.find_spec("tensor_loader") else print("Tensor is not installed here anymore: remove this line from init.py")
    
  4. Start Nuke and go to First launch below.

To uninstall, close Nuke, delete the Tensor folder and tensor_loader.py from .nuke, then delete init.py if it came from the ZIP, or remove the line above from yours. Your licence and update data stay in %ProgramData%\Tensor and %LOCALAPPDATA%\Tensor.

Studio deployment

A studio puts one copy of Tensor where every workstation and farm node reads it:

  1. Copy the Tensor folder (the one in the ZIP) to a server share, for example \\server\tools\Tensor. The path must be plain ASCII.

  2. Create Tensor\config\studio.json with this content:

    {"updates": "off"}
    

    Tensor's own updater then reads and writes nothing: the deployed version is the one everywhere, and your IT updates it by replacing the folder. A studio copy with updates off gets no advisory from Nuke either (see Updates and security advisories below).

  3. Add the folder to NUKE_PATH for every user (a machine or user environment variable, or your launcher's), for example NUKE_PATH=\\server\tools\Tensor. Or call nuke.pluginAddPath(<the Tensor folder>) from a studio init.py; never from menu.py, which runs too late: Nuke would load nothing, silently.

  4. Do not use the ZIP or the installer on those machines. If someone does, the studio copy loads, the personal one prints a line naming the winner and loads nothing: Tensor loads one copy only, the first on NUKE_PATH.

Tensor is licensed per computer (%ProgramData%\Tensor\license): the share carries the code, not the licence. Each computer signs in once (see below).

The files of the config folder. The package already ships three, and your studio.json is the only one IT creates:

File What it is
update_keys.json the pinned update-signing keys: the updater accepts an update only from one of them
version_floor.json the lowest version this install may take from a signed index ({"schema": 1, "floor_version": "<version>"})
client.json the portal address, the update endpoint and the flags of the release (a release package only). Do not edit it: the client refuses a value it does not trust and falls back to its defaults with a reason

studio.json has one key, updates:

Value Effect
{"updates": "off"} the updater never reads, downloads or writes anything, and the version in place is the version everywhere
"off", "0", "false", "no", "disabled" as the value the same ("off" is the one to write)
anything else, or a missing file updates are on

The environment variable TENSOR_UPDATES=off does the same as the file, for one machine or one launcher. Keys the client does not know are ignored, and a file it cannot read leaves updates on. TENSOR_NO_DELEGATE=1 is a support switch: Tensor loads the deployed version and touches nothing else.

A studio pilot in the beta. A studio evaluation is by quote and subject to signed terms: write to support@tensorndk.com. No pilot starts before those terms are signed, so do not put Tensor on client work first. Until then a studio uses the beta like anyone else:

  • Each artist creates their own account, with their own email address. Accounts are personal: do not share one, and do not create accounts for colleagues. The trial is one per person (verified address, Google account and computer), and the beta terms forbid creating accounts to get more trials.
  • Each computer signs in once, with the account of the artist who uses it. The licence is per computer and is shared by every Windows user of that computer, so one sign-in per machine is enough.
  • There is no studio admin view in this beta: each account sees only its own licence. Keep your own list of who has an account on which computer.
  • The first sign-in on a computer creates %ProgramData%\Tensor\license and gives every Windows user of that computer the access it needs, without administrator rights. If a Windows user cannot use that folder, Tensor says so in Settings with the folder's path: an administrator then has to fix its permissions.
  • Security advisories: with updates off, nothing arrives in Nuke. Watch the security page and give us a contact address there through security@tensorndk.com, so an advisory reaches the person responsible even though Nuke never checks.

Activation is the same on every machine and needs a browser on that machine (First launch below): a share on its own does not make a node licensed.

First launch

  1. Start Nuke. The Tensor menu appears in the node menu with Generate (TMask, TNoise), Color (TColorRamp), Blur & Sharpen (TBlur), then Settings… and About Tensor, which shows the version.
  2. Open Tensor → Settings… and press Sign in.
  3. Your browser opens on the Tensor portal. Sign in with your email and password, or with Google, and approve this computer. Settings shows a short code while it waits; check that the browser shows the same code.
  4. Back in Nuke, Settings says the licence is valid. Nodes already in your script come back to life without restarting Nuke.

TGain stays in the package as the technical reference node of the kit and has no menu entry: a saved script that uses it still opens and renders, and there is nothing to pick from the menu for it.

The licence is stored once per computer, in %ProgramData%\Tensor\license, and is shared by every Windows user of that computer. Your 14-day free trial starts with this first activation. A licence covers one computer per seat: the Trial Pro and Solo cover one computer, and the Studio plans are as the pricing page says. Moving a paid seat to another computer is possible from the portal; the trial stays on the computer it started on.

If you do not see the menu, Nuke prints one line in its console naming the Tensor folder it looked at and why it did not load it (for example a Nuke version or an operating system the package does not cover). You can also run import nuke; print(nuke.pluginPath()) in the Script Editor and look for the Tensor folder in the list. A second Tensor folder on NUKE_PATH is ignored: the first one wins.

Offline use

After activation your licence is stored on your computer, signed and tied to it. Rendering never contacts our servers. At start-up Nuke checks the licence in the background without waiting, and it keeps working for up to 30 days without a connection. Scenes and images are never sent to us.

The licence in %ProgramData%\Tensor\license is dated from the day it was issued, and what it allows depends on which licence it is:

  • A trial lasts 14 days from the first activation on that computer, and its licence ends with the trial. Settings therefore shows it active and due for an online refresh from day 5: the trial's licence is dated so that it ends exactly with the trial, not 30 days after it. Signing in again does not extend a trial — once the 14 days are over the portal answers that the trial has ended and stores no licence, so the nodes stay red.
  • A paid licence (from the sale; none is sold during the beta) is valid for exactly 30 days from the day it was issued, and Settings says when it is due for an online refresh, about day 21. A renewal is a sign-in: connect the computer once and press Sign in in Tensor → Settings…; the browser approves the machine and a fresh 30 days are stored.

On the day the stored licence ends — the last day of a trial, or 30 days after a paid licence was issued without a renewal — this is exactly what happens:

  • Every Tensor node is red as soon as Nuke validates it, with Tensor: the licence has expired (LIC_EXPIRED) in the node's error. A refused node outputs nothing — not even its input — so the render of everything below it stops, and a Write fails with that reason and writes no file. Your scripts and the images already on disk are untouched.
  • Tensor → Settings… says Licence ended.
  • With a paid licence, connect the computer to the internet once and sign in again in Settings: a fresh licence is stored and the loaded nodes render again without restarting Nuke. If one node stays red, move to another frame or reopen the script: Nuke asks the licence again for each new render. A trial cannot be renewed: your scripts stay intact and the nodes stay locked until a paid licence exists.

A computer that cannot reach the internet at all, or one behind a proxy that allows nothing, cannot be activated on its own: an isolated network is a case to talk about with us first — write to support@tensorndk.com before you plan the deployment.

Render farms

There is no render-farm licence during the beta. Farm and headless nodes are not licensed in the beta, and the pricing page Studio Site line (the whole studio and its render farm, by quote) is the plan for when the sale opens, not something you can get today.

Every Tensor node is activated on its own computer, with a browser on that computer and the internet: a node with no browser cannot be activated on its own, and there is no offline activation file to copy around. If you run a farm, or plan to, write to us before you install anything: contact us.

Updates and security advisories

Updates come from inside Nuke, and they are signed. When Nuke starts, Tensor looks for a newer version in the background and prints one line in the console if there is one. Tensor only accepts an update whose signature and SHA-256 check out. In Settings, Check for updates looks again and Install at next start installs it when you restart Nuke. If the new version fails to start three times in a row, Tensor goes back to the previous one from the next start.

A studio copy with "updates": "off" (see above) never looks for updates: your IT decides the version. Nothing then tells you about a security advisory from inside Nuke, so watch the security page — that is where advisories are published — and write to security@tensorndk.com, which is also the address to report a problem in Tensor itself.

Problems

To report a problem, use Report a bug / Send feedback in Settings, or write to the contact addresses. For a security problem, write to security@tensorndk.com: see the security page.

Tensor

Native bricks for Nuke artists.

ProductFeaturesInstall guideHow it worksPricing
ResourcesFAQAccountContact
LegalLegal noticePrivacyCookiesBeta termsSecurityEULA — planned
© 2026 Tensortensorndk.com