Skip to content
HONTRAN.DEVCreative Development

WebGLthat earnsits weight.

Three.js, React Three Fiber and GLSL for digital experiences where real-time rendering actually adds something.

Three.js · R3F · GLSL · WebGL

The plane above is live. Step through what the renderer adds to a picture — or move across it to X-ray the build.

  1. 01

    DOM image. A plain <img>: sharp, accessible, free. For a still picture, the DOM wins.

  2. 02

    Displacement. Rows of pixels shifted in the fragment shader as one image hands over to the next.

  3. 03

    Depth. The same flat quad, ray-cast as a curved surface in perspective.

  4. 04

    Shader. The pixels re-drawn as a blueprint: grid, curves, a mesh read from the image.

  5. 05

    Image. And back to the picture, untouched. On this device you get the static plate — tap X-ray.

05 cases

Use it when CSScan’t tell the story.

A canvas costs memory, battery and accessibility work. It is worth that cost when the idea genuinely needs real-time rendering.

  1. 01

    Product

    Interactive 3D product experiences.

    CSS can’t — light a surface or turn a real mesh in the hand.
  2. 02

    Image

    Displacement, distortion and transition effects.

    CSS can’t — move pixels inside an image.
  3. 03

    Space

    Camera-driven scenes and spatial storytelling.

    CSS can’t — put a camera inside a scene.
  4. 04

    Particles

    Transformation, decomposition and simulation.

    CSS can’t — move thousands of points every frame.
  5. 05

    Narrative

    Scroll-controlled visual sequences.

    CSS can’t — render a scene per scroll position.

DOM / WebGL split

Not everythingneeds a canvas.

The best WebGL implementation knows where to stop.

  1. Navigation

    DOM

    Needs focus states, real links and a screen reader. A canvas has none of that.

  2. Text

    DOM

    Selectable, translatable, indexable and sharp at every size.

  3. Content

    DOM

    Edited in the CMS; the layout reflows by itself.

  4. 3D product

    WebGL

    Light, rotation and material that only a renderer can compute.

  5. Shader transition

    WebGL

    Pixels moving inside images, beyond anything CSS can blend.

On From Another the rule was WebGL for the hero moments, DOM for everything else — and the canvas mounts only when its section is on screen.

This page — measuring…

03 patterns · all live

Three patterns,in production.

Each one solves a different rendering problem — and each one ships to real visitors, not a demo reel.

Image displacement

Pattern 01 — From Another · 2026

From Another — website hero, soft red and pink gradient with the fromanother wordmark
Technique
GLSL displacement for the cinematic transitions between work pieces; the canvas mounts only while its section is on screen.
Role
Creative Development · design by Huy Phan
Result
Live production · Awwwards SOTD · FWA FOTD · CSSDA WOTD

Spatial light

Pattern 02 — Iventions · 2025

Iventions — homepage, Step into the Spotlight, event photo collage on lavender and beige
Technique
A Three.js spotlight and image treatment — light, reveal and displacement around each image, never on top of it. Textures at full resolution, respecting pixel ratio and source aspect.
Role
Creative Development · with SERIOUS.BUSINESS and Huy Phan
Result
Live production · Awwwards SOTD + Developer Award · CSSDA WOTM

Particle / shader

Pattern 03 — hontran.dev · live

The hontran.dev LED dot field: a grid of glowing points forming a portrait of Hon Tran
Technique
A static grid of points; every shape is per-cell tone sampled from an image, and transitions dissolve through smooth noise instead of moving the dots.
Role
Design and development
Result
Live on hontran.dev — desktop only, by design. Phones get a static layout.

The plane at the top of this page

The shader isthe visible part.

The production work is everything around it.

  1. 01

    One full-screen quad in its own WebGL2 context — nothing else to draw.

  2. 02

    No camera object: perspective is ray-cast per pixel, with a focal length taken from the viewport.

  3. 03

    The curve is maths, not a mesh — a cylinder intersection computed in the fragment shader.

  4. 04

    A brushed-metal frame, lit from the pointer, computed per pixel.

  5. 05

    Three project images, uploaded once with mipmaps; anisotropic filtering where the GPU has it.

  6. 06

    One fragment program: transitions, blueprint passes and the X-ray lens.

  7. 07

    Grain and the scan band live in the same pass — no extra render targets.

  8. 08

    Headline, copy, buttons, the stage rail and an <img> for screen readers stay in the DOM.

Measured on this page, never benchmarked

The GPU hasa budget too.

Every effect is paid for in pixels, memory and battery. The numbers in blue are read from your browser right now.

01

DPR

Shaded pixels grow with the square of the pixel ratio.

Capped at 2 on high tier, 1.5 on mid; drops by half a step when frames run slow.

—

02

Textures

Every image sits in GPU memory at full size, plus mipmaps.

Three images, uploaded once, reused for every transition.

—

03

Draw calls

Each call is CPU-to-GPU overhead, every frame.

One call per plane per frame.

—

04

Geometry

Vertices cost before a single pixel is drawn.

Four vertices; the curve is solved per pixel instead of modelled.

—

05

Video

Decoding and re-uploading video each frame is the heaviest texture there is.

None on this page — stills only. On builds that need it: poster first, paused offscreen.

—

06

Memory

Contexts and textures leak when nothing disposes them.

Released on dispose; a lost context falls back to the static plate by itself.

—

07

Battery

An idle canvas still burns power.

The loop pauses offscreen and in hidden tabs; reduced motion renders only on change.

—

Desktop — full

You

High tier · capable GPU

  • WebGL plane, lens and tilt
  • Pixel ratio up to 2
  • Scroll-driven sequences

Mid-range — reduced

You

Mid tier · fewer cores or less memory

  • WebGL plane
  • Pixel ratio up to 1.5
  • Resolution drops on slow frames

Phone / low power — fallback

You

Phones, software GPUs, data saver

  • Static plate, no canvas
  • CSS scan band, tap to X-ray
  • Same content, same order

Same idea · less cost

Same idea.Less cost.

A specialist does not run heavy WebGL everywhere by default. The fallback is designed, not whatever is left when the canvas fails.

Desktop — WebGL planelens · tilt · shader

You’re looking at the fallback now

Phone — static plateno canvas
  1. 01
    Simplified shader

    Fewer passes, lower resolution, the same look.

    Per project
  2. 02
    Video

    The desktop render, pre-recorded as a light loop with a poster.

    Per project
  3. 03
    Static sequence

    Key frames of the effect, revealed with scroll.

    Per project
  4. 04
    DOM-based alternative

    An image, a CSS scan band and a tap toggle — this page on a phone. The hontran.dev dot field goes further: desktop only.

    Used here

Phones get the idea, not the bill.

Capability index

  1. 01

    3D product heroes

  2. 02

    Shader transitions

    From Another
  3. 03

    Particle systems

    hontran.dev
  4. 04

    Image effects

    Iventions
  5. 05

    Scroll-driven 3D

  6. 06

    Existing-site WebGL integration

    Your stack, your repo
  7. 07

    R3F / Three.js support

    For teams mid-build

Who owns what

Three ways to use me.

01

Full creative build

Hon owns
Front-end, motion, WebGL, responsive, integration, production
You own
The brief and the sign-off
The whole system

02

Specialist layer

Hon owns
The rendering problem
Your team
Owns the site, the stack and the release
How I plug into a team

03

Prototype

Hon owns
The difficult 3D or shader concept, proven in the browser before the full build begins
Useful for
Agencies and studios de-risking a pitch
Pitch support

After the proof, not before it

Technology supportsthe story.

It is not the story.

  1. Three.js

    This pageNot used — one quad doesn’t need a scene graph. Iventions does.

  2. React Three Fiber

    This pageNot used here. The default when a React site needs a real scene.

  3. GLSL

    This pageThe plane’s fragment shader.

  4. WebGL

    This pageWebGL2, in its own context.

  5. GSAP

    This pageEvery tween, and the one clock that drives scroll and render.

  6. Next.js

    This pageThe production site. This page is rendered by it.

  7. Blender / asset pipeline

    This pageNot needed — no models here. On product work, the part that decides load time.

From the notes

Want the engineering version?

  1. 01Hire a WebGL / Three.js Developer (Buyer’s Guide)Studio noteWebGL · Hiring9 min
  2. 02WebGL Website Examples (2026): What Makes Them WinStudio noteWebGL · Examples8 min
  3. 03Three.js Performance Optimization: A Practical GuideEngineeringThree.js · Performance8 min
  4. 04Why Your WebGL Hero Disappears on Browser BackEngineeringWebGL · Debugging10 min
  5. 05WebGL Displacement Hover Effect (Image Shader Guide)EngineeringGLSL · Shaders8 min
  6. 06White-Label WebGL Development, No In-House HireStudio noteAgency · White label7 min

Concept, storyboard or Figma

Have a scenethat shouldn’tbe fake?

Send the idea, the storyboard or the file. The first reply says whether it needs WebGL at all — and what it will cost the GPU if it does.