Three steps to a video.
Chrome shapes
A metallic orb in five shapes: spikes, tendrils, splinters, starburst, and iris bloom. Three finishes: cool blue-white steel, black chrome over cyan, and near-monochrome mercury.
The technical layers
This is what makes it depthcore rather than just shiny. Drifting outlined ovals, a scrolling block of text you can set yourself, thin angular rays across the frame, and a HUD instrument layer.
Pixelation
An optional effect that makes the whole frame read like an old screen filmed on a camera rather than a clean digital export. You control how heavy it gets, from barely there to fully degraded.
The layers that make depthcore work
The chrome is the easy half. What sells depthcore is everything cluttering the frame around it.
Where the look comes from
Depthcore and MetalHeart descend from a specific moment: late-90s and early-2000s digital art, software packaging, demoscene graphics, and the visual language of interfaces that were trying hard to look advanced.
The revival has stuck around because it is legible. Chrome, HUD elements, and dense technical text read instantly as a mood, which is exactly what you want from a visual that has three seconds to land in a feed.
Chrome alone is not enough
The common mistake is stopping at the metal. A polished chrome object on a dark background is a product render, not depthcore. The aesthetic needs the supporting layers:
- HUD instrumentation, implying the object is being measured by something.
- Dense scrolling text, which reads as a system doing work rather than decoration.
- Angular rays and outlined shapes that give the frame structure behind the subject.
- A degraded screen feel, so it looks captured rather than freshly exported.
Why it is a good fit for audio
The aesthetic is built around the idea of instrumentation, of readouts responding to something. A visualiser makes that literal: the form actually is reacting to a live signal, and the HUD layers are sitting around something that genuinely moves with your track.
That is the argument for generating it rather than assembling it in an editor. Hand-built, the reactivity is faked with keyframes and the layers sit still. Here the chrome genuinely follows your track and the layers drift behind it, which takes about a minute rather than an evening.
BeatVisualiser vs Editing it by hand
Same output. A fraction of the time.
| Feature | BeatVisualiser | Editing it by hand |
|---|---|---|
| Chrome material | Built in | Build it yourself |
| HUD / text layers | Toggle on | Design each one |
| Reacts to your audio | Manual keyframes | |
| Pixel screen look | Built in | Plugin or manual |
| Time per clip | Under a minute | Hours |
What is the depthcore aesthetic?+
What is MetalHeart in this context?+
What makes it different from just a shiny 3D render?+
Can I put my own text in it?+
What does the pixel effect do?+
Does it react to my music?+
Your track deserves a better visual than a waveform screenshot.
Drop your audio. Have a video ready to post in under a minute.
Try the depthcore orb