Launch App
Aiming for TouchDesigner?

Your stepping stone to TouchDesigner

TouchDesigner is the industry standard for real-time visuals — and eventually worth learning properly. But it means a real install, a license decision, and six different kinds of operator to get oriented in before you've made anything. VerkLabs teaches the same underlying idea — typed nodes wired together, driving shading, motion and live behavior in real time — free, in your browser, no install. Work through this path, and the instincts, the vocabulary, and a lot of the individual building blocks will already feel familiar when you get to TD.

1

Materials & shading

closest match to TD's MAT family

Start here — this is the one place the vocabulary translates almost node-for-node. Every object gets its own graph, structurally a GLSL MAT: one network compiling to that object's shader, exactly the way every Geometry COMP in TD carries its own MAT.

Later, in TouchDesignerHere, in VerkLabsWhy it matters
PBR MAT / Phong MATRGBA · PBR LightingSame lighting math, plus six ready presets in RGBA → Lighting: Matte, Plastic, Rubber, Satin, Brushed Metal, Polished Metal — so you're not dialing metallic/roughness from scratch.
GLSL MATMath · f(x)→FloatVectors · f(v,w,x,y,z)→Vec3The same write-your-own-shader escape hatch, one expression per node instead of one big block.
Constant MAT / color pickerRGBA · RGBA Color, HSLA · HSLA ColorSame idea.
Vertex displacementVertex Out · →Position, Vertex Out · →Position & NormalTD splits this across a Point SOP and a GLSL MAT; here it lives in the same graph as shading.
Try this first: wire a noise node into RGBA · PBR Lighting's roughness input and watch a material go from chrome to brushed metal in real time. That instinct — a value from anywhere feeding a shading parameter — is the whole idea, in either tool.
2

Textures & image effects

covers most of TD's TOP family

Every 2D-image idea from TOPs has a node here — noise, blur, feedback, edge detection, color grading. The one thing missing is the standalone pipeline: in VerkLabs a texture always lives inside one shape's shader, not as something you can preview or route on its own.

Later, in TouchDesignerHere, in VerkLabsWhy it matters
Movie File In / Camera InSource Data · Video, Image, CameraDirect match.
Noise TOPAnimated Values · UV Simplex, UV Fractal Brownian, UV Turbulence Noise, UV Ridge NoiseThe same four noise families, as separate nodes instead of one dropdown.
Feedback TOPSource Data · Feedback, Feedback DepthDirect match — last frame's render, read back as a texture.
Composite TOPMixing & Selecting · Alpha Blend, RGBA + RGBA, Screen, OverlayDirect match — over/add/screen/overlay blending.
3

Motion & control

a real strength, not just a CHOP substitute

CHOPs are how TD turns an LFO, an audio band, or a timeline into motion. But wiring up a whole show — several tracks mixed together, visuals precisely timed off them — is usually something you build yourself, from Timeline CHOPs, Audio Device/File In CHOPs and custom logic tying it all together. VerkLabs gives you that as one authored surface from the start: the Runsheet.

Worth celebrating

Mix multiple audio tracks, then drive camera moves, parameters and on-screen overlays off exact frames or beats — all authored directly on one timeline, with no external sequencer or scripting required to get a synced show running. A Camera track · Move or Camera track · Path event sets your camera's position every frame, the same job an exported CHOP channel does driving a Camera COMP's transform in TD. A Params track sets a numbered parameter slot over time, the same way you'd bind a channel to a custom parameter. Audio, video, on-screen text and visibility all run on that same timeline, in sync — the carefully-timed, audio-reactive show TD can build, but doesn't hand you ready-made.

Later, in TouchDesignerHere, in VerkLabsWhy it matters
LFO / Wave CHOPAnimated Values · Square Wave, Sinus Wave, Sawtooth WaveDirect match, feeding one shader input.
Audio File In + Analyze CHOPSource Data · Microphone, Audio Track — Source Values · Frequency Volume10-band or 256-band frequency data from mic, mixdown, or a file — direct match.
MIDI In / OSC Innot yetThe biggest gap here — no live MIDI or OSC input today.
Drive any parameter from a timelinethe RunsheetReaches into camera, audio, parameters and overlays — not into the node graph itself.
4

Geometry

thin, on purpose

TD builds meshes procedurally, SOP by SOP. VerkLabs' Builder tool creates your geometry instead — the node graph only displaces the vertices a mesh already has, and drives point-based effects like particles through a small GPGPU-style state system.

Later, in TouchDesignerHere, in VerkLabsWhy it matters
Sphere / Grid / Box SOPuse the Builder toolPrimitives aren't node-based here.
Point SOP / Noise SOPVertex Out · →Position, State categoryClosest match — a live per-vertex computation, not an editable point cloud.
Particle SOPState · Particle Index, Var A/BBuild-your-own from the compute-state primitives.

5 ·  What's waiting for you in TouchDesigner

Work through the steps above and you'll arrive at TouchDesigner already thinking in real-time nodes — typed sockets, shading, control signals, the habit of building complex behavior from small pieces. Here's what's genuinely TD-only, so you know what you're graduating to.

Data & scripting

Tables, JSON/XML, Python scripting, OSC and MIDI I/O — TD's DAT family. VerkLabs' raw-expression nodes cover shader math only.

Full geometry toolkit

Procedural primitives, booleans, copy/extrude/subdivide — TD's SOP family, node by node.

Components & UI

Nesting whole sub-networks — cameras, geometry, on-screen control panels — as reusable objects with their own hierarchy.

Live control surfaces

MIDI controllers, OSC, DMX — patched straight into any parameter, for real hardware in a real room.

That's the real reason to make TouchDesigner your destination, not your starting point: everything you practice here — the node-graph instincts, the vocabulary, a lot of the individual building blocks — carries straight over, so this list is what's left to learn, not everything.

Why practice here before you install TouchDesigner

No install

Open a link, start wiring nodes today. TouchDesigner means a real download and a license decision before you've made anything.

Forkable by link

Share a project the way you'd share a CodePen — useful for classmates, a portfolio, or a teacher checking your work. A TD patch is a file you email or drop in a folder.

Hand & body tracking, no hardware

Point a webcam at yourself and start experimenting. TD's equivalent usually wants a Kinect or a paid plugin.

Timeline & audio, built in

Mix multiple tracks and drive camera, parameters and overlays off exact frames or beats — no external sequencer or custom scripting required to get a synced show running.