Style Bible for Games: Structure, Examples, Budget Savings

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:

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

1. Analysis of existing materials. We pilot 3-5 assets from the project, note deviations from the expected style.
2. Structure design. We determine the list of disciplines, depth of elaboration, and document format.
3. Technical content creation. We write parameters for each discipline: polycount, texel density, PBR ranges, naming convention, shader parameters.
4. Anti-example creation. We break down typical mistakes from our experience or the client's project.
5. Testing on pilot assets. We hand the document to an artist, they create an asset per the bible—we verify the result matches expectations.
6. Finalization and deployment. We compile the document in the chosen tool (Figma, Notion, or web), set up navigation and search.

Estimated Timelines

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.

Why character concept art needs more than artistic skill

A concept artist in a game project is not an illustrator. Their job is to make visual decisions that will later be reproduced by three departments: 3D modelers, animators, and tech artists. If the concept looks beautiful but doesn't account for in‑engine implementation, the team will lose weeks interpreting the artist's intentions. With 10+ years of experience across 50+ projects (from indie to AAA), we have built a character concept art pipeline that provides answers instead of generating questions. Request a consultation via messenger — we evaluate your project within 24 hours and suggest timelines starting from two weeks.

The most common problem without a clear visual guide is stylistic drift. Initial assets go in one direction, but three months later, a new artist arrives and the new characters look like they belong to a different game. Fixing this is expensive: up to 40% extra time on retopology and texture repainting.

What does a mood board actually solve?

A mood board is not a collage for inspiration. It is a document that answers specific team questions. Color palette of the world: warm or cold, high or low saturation. The level of stylization is fixed: photorealism, semi‑realistic, cartoon, or pixel art. The readability of character silhouettes is checked at a distance. Texture detail and LOD are defined upfront.

We organize mood boards into sections: characters, environment, UI, lighting, color palette. Each section contains concrete references with annotations: "take form language from here," "lighting like this but warmer," "texture detail as in this project." Tools: PureRef for assembling references on the desktop (keeps a collage over other windows), Pinterest for gathering, Figma for structured mood boards with comments.

What does a style guide include?

A style guide is an operational document for the entire team, not just an artbook. It contains specific values:

• Color palette — not "warm tones overall," but HEX codes or Pantone. Main palette (5–7 colors), accent palette (2–3 colors), danger/UI colors. All artists work with the same values.
• Character proportions — model sheets with defined ratios. For stylized games this is critical: if one artist draws a head at 1/4 height and another at 1/6, characters look like they're from different universes.
• Form language — which shapes are characteristic of the world. Aggressive sharp angles for enemies, soft rounded for allies — a classic technique, but it must be explicitly defined.
• Line style — contour line thickness, presence/absence of outline style, variations by plan.
• Examples of correct and incorrect — concrete examples of proper application and deviations. This reduces iteration count during review by 3–5 times compared to working without a guide.

How we develop character concept art: pipeline and deliverables

We develop character concept art through a structured pipeline from brief to final turnarounds. Character concept art is one of our key competencies; we guarantee clear data handoff to the 3D department.

Step 1: Brief

Before the artist opens Photoshop or Procreate, there must be a design brief. Minimum set:

• Character role in the game (protagonist, antagonist, NPC, enemy type)
• Approximate class/archetype (warrior, mage, trader)
• World context — setting, technological level, cultural influences
• Functional requirements — if the character must be readable from 10 meters on a phone screen, that's a silhouette requirement
• Technical constraints — polygon budget, number of materials, LOD presence

The last point is often skipped by concept artists. The result: a beautiful concept with 15 materials and feather details that are 2 pixels in the actual game. Fixing technical limits in the brief saves 20–30% of 3D department time.

Step 2: Silhouettes

The first stage: 8–12 black‑and‑white silhouettes. No details, only shape. Fast (5–10 minutes per silhouette), selects direction without attachment to a specific variant. Silhouette readability is the main criterion for character design. In motion, the player perceives the silhouette before details. If a warrior's silhouette is indistinguishable from an archer's, that's a design problem.

Step 3: Refinement of selected variants

2–3 best silhouettes are detailed further. Main shapes and proportions are added, still without final render. The client sees 2–3 directions and chooses one. Tools: Procreate on iPad for quick shaping, Photoshop for final polish and material sheets.

Step 4: Color pass

The chosen variant gets a color scheme. 2–3 color variations are made — useful for client selection and future character skins.

Step 5: Turnaround and material sheet

The final concept includes:

• Turnaround — front, side, back views with proportion grid
• Material sheet — breakdown by zones: skin, metal, fabric, magical effect
• Detail sheet — close‑ups of important elements: face, hands, unique details

These documents are handed over to the 3D artist as technical specifications, not as "inspiration."

How do environment and UI fit into a unified visual style?

For environments, concept art addresses space readability and atmosphere. Tonal design (light and shadow distribution) is primary, details secondary. Each environment concept must have a clear focal point. If the eye wanders evenly, the level design is weak. Color scripting: a sequence of color decisions across acts is created for the narrative structure. Warm village level → cold blue dungeon → anxious red‑orange finale. This is not random but a narrative tool (detailed in The Art of Game Design by Jesse Schell).

UI in games is a separate discipline. Game interface must be readable in motion, under different scene lighting, and at different resolutions. We create UI concepts in Figma with explicit states: normal, hover, pressed, disabled, active.

Tools

Using Blender for 3D blocking before the final drawing eliminates perspective errors in complex angles and saves rework time. Compared to drawing from scratch, Blender blocking reduces perspective mistakes by 80%.

What is included in the final concept package?

• Concept art for characters, environments, UI — from silhouettes to final turnarounds
• Style guide with palettes, proportions, form language, and examples
• Color scripting for narrative sequence of levels
• Material sheets and detail sheets for handoff to the 3D department
• Source files in PSD/Procreate with layered structure

How does concept art reduce production time?

Good concept art, created with technical constraints in mind, reduces 3D production time by 25–30% compared to working with scattered images. The artist doesn't interpret — they reproduce. Poor concept art means constant clarifications, reworks, "well, I thought you meant..." Using a style guide reduces revision count in the 3D department by 3–5 times. For a typical character model budget of $15,000, a solid concept package saves $4,500–$5,000.

We deliver the concept package as a separate phase before starting 3D production. The client approves the visual direction before modeler work weeks are invested. Contact us to discuss your game's visual style — we guarantee transparency at every stage and capture all technical specifications within 24 hours. Request a consultation and we'll provide a timeline and budget estimate tailored to your project.