Shader Development

Visual effects that run in real time

Custom shaders and real-time graphics for game studios, interactive agencies, and web experiences. Written by someone with a 3D art background - the shader looks right because the person writing it understands why it should.

Start a Project View Portfolio

Why work with me

3D artist who writes shaders

Most shader developers come from a programming background and learn the visual side. I came from 3D art and learned the code. The difference shows in how materials look - physically plausible, not technically correct but visually wrong.

Web and game ready

Shaders delivered for your target platform: GLSL for WebGL and Three.js, HLSL for Unity and Unreal Engine, or platform-agnostic GLSL for cross-platform use.

Interactive and performant

Real-time means performance matters. Shaders are profiled and optimised for the target hardware - visually ambitious but not at the cost of frame rate.

Real projects. Real clients.

A selection of relevant work from 10+ years of practice.

WebGL Interactive Installation

Custom GLSL Shader Suite

Developed a suite of custom GLSL shaders for a browser-based interactive installation. Included procedural surface materials, dynamic lighting effects, and post-processing passes running at 60fps in-browser.

Game Studio

Unreal Engine Material Library

Built a library of custom Unreal Engine materials for a game studio - physically-based surface shaders, stylised effects, and animated environment materials. Delivered as a reusable asset library.

Frequently Asked Questions

What is the difference between a shader and a material?

A material is the visual description of how a surface looks - colour, roughness, reflectivity. A shader is the code that calculates that appearance in real time. In most engines, you create materials that reference shaders. Custom shader development means writing the underlying code rather than using built-in material templates.

Can you build interactive shaders for websites?

Yes. Three.js and WebGL shaders that run in the browser are a specific area of my practice. Product configurators, interactive backgrounds, data visualisation effects, and generative art are all possible.

How do you handle performance for mobile or lower-spec hardware?

I build tiered fallbacks for complex shaders - a high-quality path for capable hardware and a simplified path for mobile or lower-spec devices. Performance targets are agreed at the start of the project.

Need a visual effect that does not exist yet?

Describe what you want to achieve visually and the platform it needs to run on. I will tell you what is feasible.

Get in Touch