Note: when the art director is overloaded and artists interpret style on their own, a single texture mistake can spread across hundreds of assets. Without a unified document, everyone makes decisions by eye—the result: quality inconsistency, rework, missed deadlines. On one project we saw artists using three different texel densities for props in one location—40% of assets had to be retextured. That cost significant time and budget—rework alone cost over $12,000.
A style bible is not just a set of rules—it's a living document that replaces the art director in their absence. It includes not only technical parameters (PBR ranges, polycounts, naming convention, LOD0 meshes, UV layout) but also decision history, anti-examples, and update instructions. Such a document reduces onboarding time for new artists by 50% and lowers the defect rate in outsourced deliveries to 5%. Request a consultation if you want to assess the effectiveness for your project. With over 7 years of experience and 50+ completed style bibles, TrueTech guarantees a consistent art pipeline.
How to Know if Your Project Needs a Style Bible
If assets from the same set look like they're from different games, or if artists keep asking the art director the same questions—it's time. Another sign: outsourced studios send textures with incorrect PBR values that need rework. In such cases, a style bible pays for itself after the first onboarding of a new employee or delivery from a contractor. Savings on outsourced rework can be substantial—up to $15,000 per month for a mid-size project.
Why a Style Bible Saves Budget
A single texel density error can lead to retexturing 100+ assets. Rework costs can quickly add up. A style bible prevents such situations. Our clients report that savings on outsourced rework reach 60%, and art asset approval time shrinks by 70%. For example, one studio saved $8,000 in just two months after implementing our bible.
Typical Problems Solved by a Style Bible
PBR Parameter Spread
Artists often use incorrect Roughness and Metalness ranges—for example, a metal part ends up matte, and wood becomes shiny. In the bible we define a PBR Value Guide table:
| Material | Albedo HSV (Hue) | Roughness | Metalness |
|---|---|---|---|
| Rusted metal | 20–40, 0.2–0.5, 0.3–0.6 | 0.6–0.9 | 0.0–0.3 |
| Smooth plastic | 0–360, 0.1–0.3, 0.7–1.0 | 0.1–0.3 | 0.0 |
| Leather | 10–30, 0.3–0.5, 0.3–0.5 | 0.5–0.8 | 0.0 |
Inconsistent Texel Density
If one artist makes props at 1024 px/m and another at 512 px/m, the overall scene looks uneven. The bible fixes a uniform density for each category: characters 2048 px/m, props 1024 px/m, environment 512 px/m.
Incorrect Naming Convention
Files named model_v2_final_2.fbx make it hard to find assets quickly. The bible sets a template: AssetType_Category_Variant_Version, e.g., Prop_Chair_Wooden_v01.fbx.
What a Full Style Bible Includes
Vision Statement
One or two paragraphs—how does the game look when described visually to someone who hasn't seen it? Not genre, not mood—concrete images. "Post-apocalypse after 200 years: nature has reclaimed cities, rust covered in moss, metal matte with dark oxidation, light always through leaves or dust." This is an anchor for any disputed decision.
Color System with Application Rules
Not just hex codes—a hierarchy: dominant colors (60%), secondary (30%), accent (10%). For 3D—a table of allowed Albedo ranges for each material class. This eliminates physically incorrect textures that break lighting.
Typography and Font System
Primary/secondary fonts, scaling rules, margins. For games—separate rules for diegetic labels (in-world text) and UI typography.
Rules for Each Art Discipline
3D modeling (mesh naming convention, UV layout rules, maximum polycount per category, LOD0 guidelines), texturing (texel density per asset category, texture atlas resolution, required maps—BaseColor, Normal, ORM or separate R/M/AO—and Substance Painter export presets), rigging (bone naming convention, IK/FK strategy, BlendShape names), animation (curve style, timing and spacing rules for the visual style).
VFX Rules
Particle system: size, lifetime, speed ranges—all tied to the visual style. If the game is stylized, VFX should not be realistic even if technically possible. Includes shader parameters for materials.
Anti-Examples
This is the most valuable part. We show actual assets that were done "wrong" and explain why. It teaches better than any rule. Example: Metalness = 1.0 for rusted metal is physically incorrect, as explained in Physically Based Rendering documentation. Correct: use a gradient metalness mask from 1.0 (clean metal) to 0.0 (rust).
Deliverables of the Style Bible Service
Our service includes:
- Complete style bible document (PDF and editable source)
- All source files (Figma, Notion, or custom web portal)
- Changelog template and version control setup
- 1-hour onboarding session for your team
- 30 days of post-delivery support
- Option to purchase additional training or audits
How Often to Update the Style Bible?
A style bible should not be static. Best practice is versioning (v1.0, v1.1, etc.) with a changelog: what changed, why, which assets need to be updated per new rules. A document without a changelog will contradict itself in six months. Update process: who can make changes, how it's approved, how the team is notified—these are also part of the document. We recommend reviewing the bible after every major sprint. A common beginner mistake is missing a vision statement. Without it, animation may contradict the mood. Solution: include 1-2 paragraphs of imagery. Pure PBR ranges without anti-examples make artists repeat old mistakes—add 3-5 anti-examples from the pilot. Without a changelog, the document becomes outdated in six months—version it and keep a change log.
How We Create Style Bibles
- Analysis of existing materials. We pilot 3-5 assets from the project, note deviations from the expected style.
- Structure design. We determine the list of disciplines, depth of elaboration, and document format.
- Technical content creation. We write parameters for each discipline: polycount, texel density, PBR ranges, naming convention, shader parameters.
- Anti-example creation. We break down typical mistakes from our experience or the client's project.
- Testing on pilot assets. We hand the document to an artist, they create an asset per the bible—we verify the result matches expectations.
- Finalization and deployment. We compile the document in the chosen tool (Figma, Notion, or web), set up navigation and search.
Estimated Timelines
| Project Scale | Composition | Timeline |
|---|---|---|
| Indie / small team | 15–25 pages, core disciplines | 2–3 weeks |
| AA project / 15–30 people | 40–70 pages, all disciplines + anti-examples | 5–8 weeks |
| Large project / outsourced-oriented | 80–120+ pages, full system + updatable version | 3–5 months |
Cost is calculated individually. If the project already has partial documentation, we start with an audit of existing materials. Request a style bible for your project—we'll help determine the scope. Get a consultation on the document structure: send current art assets and a style description—we'll assess what needs to be added or fixed. TrueTech has delivered 50+ style bibles for over 7 years, trusted by AAA and indie studios alike. Our certified pipeline guarantees consistency and measurable savings.