Guides · 6 min read · Updated
What are good WebGL hero ideas for a SaaS website?
The best WebGL hero for a SaaS site is a single moving object that shows what the product does, such as data flowing for an API, a terrain for analytics or a globe for infrastructure. Choose one of the ten concepts below by product type, keep it to one draw-heavy effect, and check its cost on a phone before you commit.
The rule: the hero should show the product
A rotating glowing blob is easy to build and says nothing. A hero works when a visitor can guess the product from the motion before reading the headline. Data that flows suggests an API or a pipeline. A surface that rises and falls suggests analytics. Nodes that light up suggest automation.
So the method is to start from the one verb your product performs, pick the concept whose motion matches that verb, then pay attention to what it costs. Each of the ten ideas below lists the product type, the technique, the performance cost and a template from the catalog that shows something close to it.
Ten hero concepts
Costs are relative: low means a typical phone holds 60 frames per second without tuning, medium means it needs a pixel ratio cap and some care, and high means you should plan a fallback.
01A living data terrain
- Fits
- Analytics, BI and observability tools
- Technique
- A subdivided plane whose vertices are displaced in a vertex shader by noise or by a row of metric values, lit with a simple gradient.
- Cost
- Medium. About 100,000 vertices is plenty. Vertex work is cheap, fill rate stays low if you skip transparency.
- Tip
- Feed it real values from a sample dataset and the hill shape means something instead of just looking nice.
Close in the catalog: Lodgepole Live Contour Map Climate Fund
02A voice orb that reacts to sound
- Fits
- Voice assistants, transcription and meeting tools
- Technique
- A sphere shaded in a fragment shader with layered noise and a fresnel rim, with an audio level (or a fake pulse) scaling the distortion.
- Cost
- Medium. Fragment shader on a small area. Cap the pixel ratio and it holds up on phones.
- Tip
- Use a fake breathing pulse by default and connect the microphone only when the visitor presses a button.
Close in the catalog: Iridescent Voice Orb
03Packets flowing along lines
- Fits
- APIs, developer tools, CI and message queues
- Technique
- Thousands of points drawn as one instanced mesh or a Points object, moving along curves with positions computed in the vertex shader.
- Cost
- Low. One draw call. Ten to fifty thousand points is fine on most phones.
- Tip
- Make the flow show the product. Requests enter on the left, one line splits, results exit on the right.
Close in the catalog: Lumenrail Stream of Light Hosting
04A ribbon of money
- Fits
- Payments, banking and invoicing
- Technique
- A tube or ribbon along a smooth curve with an iridescent or glossy material, with the curve control points nudged by scroll.
- Cost
- Low to medium. Geometry is small. A physical material with transmission raises cost a lot, so prefer a cheap shader.
- Tip
- A calm, slow ribbon reads as trustworthy. Fast chaotic motion reads as risky for money.
Close in the catalog: Chrome Capital Fintech Platform
05A wireframe shield with a scan line
- Fits
- Security, identity and compliance
- Technique
- Line segments or a wireframe mesh, with a bright band sweeping through using a time-based uniform in the shader.
- Cost
- Low. Wireframes are cheap. Avoid bloom on phones or render it at half size.
- Tip
- Show a before and after: the scan line passes over a red area and leaves it green.
Close in the catalog: Aegis Cybersecurity Particle Scene
06A globe with arcs between regions
- Fits
- Cloud, CDN, logistics and global teams
- Technique
- A sphere textured with a dot map or drawn as points, plus curved lines between locations animated with a dash offset.
- Cost
- Medium. The dot map texture is the main download. Draw arcs with a few hundred segments, not thousands.
- Tip
- Place the arcs between the regions your product really serves.
Close in the catalog: Strait Glowing Globe Money Transfer
07Cards that assemble as you scroll
- Fits
- Workflow, project management and productivity tools
- Technique
- Planes or CSS 3D cards that start scattered and settle into a layout, driven by a scroll progress value.
- Cost
- Low. A handful of transformed planes. CSS 3D can do this with no WebGL at all.
- Tip
- End on the exact screen the product shows, so the hero hands off to a real screenshot.
08A liquid gradient that follows the cursor
- Fits
- Design tools, creative platforms and brand sites
- Technique
- A full-screen fragment shader using domain-warped noise, with the pointer position as a uniform.
- Cost
- High on phones. It shades every pixel. Render it at half resolution and scale up, which a soft gradient hides well.
- Tip
- Drop it to a static gradient for reduced motion and for phones that struggle.
Close in the catalog: Orchid AI Creative Studio
09An exploded product that reassembles
- Fits
- Hardware, devices, wearables and physical products
- Technique
- A glTF model whose parts move outward and back along axes, with the camera following a short path as you scroll.
- Cost
- Medium to high. The model file is the cost: keep it under a few megabytes, compress textures, and limit draw calls.
- Tip
- Name each part in the page text as it moves, so the motion teaches the product.
Close in the catalog: Halo Headphones Exploded View
10A network graph that lights up
- Fits
- AI agents, automation and integrations
- Technique
- Instanced spheres for nodes, one line-segments object for edges, and a highlight that travels along the path of a running task.
- Cost
- Low to medium. Instancing keeps it to a few draw calls even with hundreds of nodes.
- Tip
- Light the path that matches the step the user is reading about, so the graph follows the story.
Close in the catalog: Agent Swarm Force Graph
How to choose among them
Write one sentence that starts with your product's main verb: it sends, it measures, it protects, it connects, it assembles. Match that verb to a concept. Sending suggests flowing points, measuring suggests a terrain, protecting suggests a scan, connecting suggests a globe or a graph, and assembling suggests parts that come together.
Then check the cost column against your audience. If most of your visitors arrive on phones, favor the low-cost concepts, or build the medium ones with a pixel ratio cap and a still fallback. If your buyers are on desktops, you have more room, but the page still has to load quickly and stay readable.
Finally, test the headline over the scene at its busiest moment. If you cannot read the words while the motion peaks, reduce the contrast of the scene behind the text, not the size of the text.
How to read the performance cost
WebGL heroes are limited by three things, and each concept stresses a different one.
| Limit | What causes it | How to cut it |
|---|---|---|
| Fill rate (pixels shaded) | Full-screen fragment shaders, transparency, bloom, large pixel ratio | Cap the pixel ratio, render at half size, avoid stacked transparent layers |
| Draw calls | Many separate meshes or materials | Use instancing, merge geometry, share materials |
| Download size | Models, textures, video | Compress textures, simplify meshes, load after first paint |
| Main thread | Heavy JavaScript per frame, large garbage | Move work into shaders, reuse objects, avoid allocation in the loop |
A full-screen liquid gradient is almost all fill rate. A particle flow is almost all vertex work and one draw call. A product model is mostly download size. Knowing which limit your concept hits tells you where to tune.
A hero that scales itself
Whichever concept you choose, build in a quality dial from the start. Here is a small controller that lowers the pixel ratio when frames run long, which saves a slow device without touching a fast one. The phone performance guide covers the measurement in detail.
// Call once per frame with the time since the last frame, in milliseconds.
let ratio = Math.min(devicePixelRatio, 2);
let slow = 0;
export function adapt(renderer, frameMs) {
slow = frameMs > 24 ? slow + 1 : Math.max(0, slow - 1);
if (slow > 30 && ratio > 1) {
ratio = Math.max(1, ratio - 0.25);
renderer.setPixelRatio(ratio);
renderer.setSize(innerWidth, innerHeight, false);
slow = 0;
}
}What to avoid in a SaaS hero
- Motion that hides the headline. The value proposition has to stay readable on top of the scene at every moment.
- A scene that needs 3 seconds to appear. Show a poster or a gradient immediately, then fade the canvas in.
- Shipping the effect to everyone. Visitors with reduced motion, data saving or a weak GPU should get a still image.
- Using the same effect as every other product. Tie it to your own verb, as the ten ideas above do.
- Forgetting the page below. A heavy hero that never pauses drains the battery while people read pricing.
For a full walk-through of loading three.js and running a clean loop, see how to add three.js to a website.





