Where native Framer stops
Custom code components and WebGL
Framer covers most of a marketing site. When it runs out — an interactive pricing model, a calculator, a live product demo, a scroll-driven 3D scene — I write the React component or the shader and drop it onto the canvas, where your team keeps editing everything around it as normal.
$7,000
Custom builds start here
React + GLSL
What actually gets written
60 fps
The frame budget I build to
Six things I get asked for most
Every panel below is running live in your browser right now — same technique, same code, no video files.
Shaders that answer the cursor
GLSL-style noise fields rendered every frame. No video file, no loop seam, and the field bends toward wherever the pointer is.
Real geometry, not a picture
Objects projected and drawn live — product spins, exploded views, hero shapes that turn while you scroll.
Scroll-scrubbed timelines
Sections that play forward and backward with the scrollbar, keyframe by keyframe, instead of fading in once.
Motion with weight
Springs, damping and repulsion, so elements settle and overshoot the way physical things do.
Live numbers, not screenshots
Charts drawn from real data at load, so the page never quietly goes out of date.
Configurators and multi-step flows
Quote builders and onboarding flows that hold state across steps and compute a real answer on the page.
When this is worth paying for, and when it is not
Hover any line to see what ignoring it actually costs.
How a component actually ships
Spike
I build the risky part first, alone, and send you a link to click. If the idea does not survive contact with a real browser, we find that out in days rather than at the end of the project.
Wire
The component moves onto your canvas with property controls attached, so you change copy, colours and numbers from the Framer sidebar without ever opening the code.
Hand over
The code file lives inside your Framer project. No external repo, no build step, no service to keep paying for, and nothing that breaks the day I stop answering email.
What it costs
Quoted per component
Most components take between a day and a week. Each one is priced before it starts and folded into the wider project, so nothing appears on the invoice you did not agree to.
$7,000
and up
Code components, WebGL and advanced scroll systems as the project itself, scoped per project after we agree what has to exist.
Questions people ask before starting
Can Framer run custom React code?
Yes. Framer has first-class code components: a React file lives inside the project, shows up in the layers panel like any other layer, and exposes property controls so the rest of the team edits it from the sidebar.
Will a custom component slow my site down?
It does not have to. Canvas and WebGL work is gated so it only animates while on screen, it respects prefers-reduced-motion, and it falls back to a single static frame on low-power devices. I build to a 60 fps budget and check it before handover.
Do I actually need WebGL, or is canvas enough?
Most effects people call WebGL run fine on a 2D canvas, which is lighter and works everywhere. I reach for WebGL when the scene genuinely needs shaders or real depth — not by default.
What if I want to change it later?
Anything you are likely to change becomes a property control: text, colours, speed, counts. For deeper edits the code file sits in your project, commented and readable.
Can you add a component to a site I already have?
Yes, and that is most of this work. Your site does not need rebuilding — the component drops into the page you already have.
Does custom code hurt SEO?
Not if the meaningful content stays as real text on the page instead of being drawn inside the canvas. I keep animation decorative and content in the DOM, so crawlers still read everything.
Describe the thing Framer will not let you build
A sentence is enough. I will tell you honestly whether it needs custom code, whether a marketplace component already covers it, or whether the idea should change shape first.