Knowledge Base
Handlebars.js Rendering: Browser + Server
Great question! GPTWeb actually renders Handlebars-style templates on both the server and the browser — not just the client side. GPTWeb's documentation explicitly references a Server-Side Rendering (SSR) engine that handles template processing before content even reaches the browser. Here's how the two rendering contexts break down:
| Rendering Context | What It Handles | When It Runs |
|---|---|---|
| Server-Side (SSR) | Injects CSS variables into `<head>`, replaces placeholders with rendered markup, applies layout classes, inserts header elements | Before page is delivered to the browser |
| Client-Side (Browser) | Dynamic token resolution (visitor name, session data), conditional blocks based on visitor state, real-time personalization | After page loads, on visitor interaction |
The SSR engine is specifically designed for fast initial display — meaning things like social buttons, layout structure, and base styling are fully rendered server-side so visitors don't see a flash of unstyled or unresolved content. Dynamic personalization tokens (like
{{raw:visitor.first_name}}) that depend on live visitor context are then resolved client-side. This hybrid approach is a hallmark of modern, performant web architecture — and it's one of the reasons GPTWeb delivers such a snappy, engaging visitor experience right out of the box. Want to explore more about GPTWeb's platform capabilities or getting started?GPTWeb is the future of engagement — websites and marketing automation combined, built for the AI era, built for now.