// Tech

Troika Three Text — High-Quality Text in 3D Scenes

Troika provides anti-aliased, accurate, performant text rendering in Three.js — essential for typography-heavy 3D sites.

Get a quote All 3D services

Troika Three Text (protectwise/troika) renders accurate, anti-aliased text in Three.js scenes via signed distance fields. Compared to Three.js's default TextGeometry: significantly better visual quality (no jagged edges), much smaller bundle (fonts streamed as needed), proper kerning and ligatures. Use cases: typographic 3D heroes (large text floating in scene), labels for interactive 3D objects, scrollytelling chapters with text composed in 3D space. Drei has a `<Text>` component that wraps Troika for R3F use. For premium typography-driven 3D sites, Troika is essentially required — Three.js's default text is not at the same quality bar.

What you get hands-off

After delivery: source repository on GitHub (private), commented code, a 5-min Loom walkthrough explaining the scene logic, and the asset pipeline documented. First year of hosting and minor revisions is included. After that we agree on a maintenance plan if needed.

What this delivers

Concrete output: a working troika three text integration on a real production site, not a demo. The integration includes device-tier detection so weak phones get a lighter version automatically. Source files are handed over in their original formats — Blender, GLSL, glTF — so any future developer can continue where I stopped.

How I work with it

On a typical project, troika three text ships as a self-contained module: one entry-point JS file, one CSS file, asset bundle below 1.5MB total. I keep the integration sandboxed so the rest of the site stays SEO-friendly classical HTML. Frame budget targets 60 FPS on a mid-range Android, with a measurable fallback below.

Performance budget

Lighthouse mobile target: 85+ across all categories. I measure on real devices, not just emulator. Asset compression: glTF + Draco for meshes, KTX2 for textures, Brotli for shaders. Lazy-load any troika three text scene that isn't above the fold so the first paint stays under 1.5s.

Frequently asked questions

Why pick this technology over alternatives?

It has the largest production-quality ecosystem, the most documentation, and the most experienced developers available. For a site you want to maintain for 3+ years, ecosystem maturity matters more than feature peak.

What if a newer tool comes out next year?

I track new tooling and migrate when it makes sense, but only after the new tool ships stable production releases for at least 6-9 months. I don't rebuild client sites on bleeding-edge tools — that's the path to broken sites.

How long does this take?

Standard scope: 4-6 weeks from contract signature to live site. Larger scope (configurator, multi-scene scrollytelling) takes 8-12 weeks. Rush projects (2-3 weeks) are accepted with a 30-40% rush surcharge.

What does it cost?

Hero-section 3D upgrade: \$1,500-\$2,500. Full multi-scene 3D site: \$3,500-\$8,000. Configurator with custom shaders: \$5,000-\$12,000. All fixed-price, source code included. EUR equivalents on request.

What if my visitors are on weak phones?

The site detects device tier before the first scene loads and serves a lighter version on weak hardware (fewer particles, simpler shaders). Devices without WebGL get a static fallback that preserves the visual language and conversion path.

Ready to ship a 3D experience?

Tell me what you need — fixed price, fixed deadline, no surprises.

Get a quote +381 61 224 8989