# 51% of Japanese Game Studios Now Use Generative AI, 32% Building Engines In-House

> CESA says 51% of Japanese studios now use generative AI, led by visual asset creation. 32% apply it to in-house engines, signaling AI as a core production tool.

- Type: AI news
- Page: https://completeaitraining.com/news/51-of-japanese-game-studios-now-use-generative-ai-32/
- Published: 2025-09-28
- Updated: 2025-09-28
- Author: Jeroen Erne
- Jobs: IT and development
- Reading time: 3 min

### More Than 50% Of Japanese Studios Use Generative AI In Game Development

**Date:** September 27, 2025

Japan's CESA reports that **51% of domestic game studios now use generative AI** in development. The survey, conducted across 54 studios in June-July 2025, shows the most common use case is **visual asset creation** (e.g., character images), with **32% building or augmenting in-house engines** using AI.

Adoption spans AAA and indie teams alike. Studios are using AI for asset generation, story and text, prototyping, tool automation, and increasingly, engine-level workflows.

#### Why it matters for engineering and product leads

- **Production velocity:** Faster content pipelines and prototyping shift schedules left. Expect shorter time-to-first-playable and iterative balancing.
- **Cost structure:** Asset throughput rises while unit cost drops, pushing teams to re-evaluate vendor spend, outsource mixes, and headcount plans.
- **IP and compliance risk:** Model training data, licensing, and content provenance need policy and tooling-especially for shipped assets and narrative.
- **Org design:** AI-first pipelines create new roles (prompt ops, data tooling, AI QA) and reshape art, design, and engine teams.

#### What the CESA data highlights

- **51% of studios use generative AI** to support development.
- **32% leverage AI for in-house engines**\-from code generation and profiling aids to content pipelines and tooling.
- **Primary use:** Visual assets (concepts, characters), followed by **story/dialogue** and text utilities.

Major Japanese publishers have publicly discussed AI initiatives in recent months, and smaller teams are following suit. The signal is clear: AI is moving from experiment to standard practice.

#### Practical moves for studio tech leadership

- **Define an AI usage policy:** Approved tools, model sources, data retention, and review gates for shipped content.
- **Set human-in-the-loop checkpoints:** Art direction, narrative approval, code reviews, and legal/IP sign-off-before content hits main branches.
- **Establish asset provenance:** Track prompts, seeds, model versions, and licenses. Store metadata alongside source files.
- **Segment model strategy:** Public models for exploration, fine-tuned or on-prem models for production-critical or IP-sensitive work.
- **Instrument the pipeline:** Time-to-asset, review cycle count, defect/bug rate, localization coverage, and cost per asset-measured pre/post-AI.
- **Guardrails for code:** Static analysis, unit + property tests, and fuzzing on AI-assisted engine/tooling contributions.
- **Cost controls:** Token budgets, job quotas, and caching to keep inference spend predictable.

#### Engine and tools: build vs. buy with AI in the loop

With 32% using AI for in-house engines, the line between engine and content pipeline is blurring. Teams use models for code scaffolding, shader iteration, asset importers, and tool UI generation.

- **Build if** your differentiators are engine-deep (networking, animation, tooling fit to your genre) and you can keep a tight review loop.
- **Buy/extend if** platform reach, ecosystem plugins, and hiring velocity outweigh control-then add AI layers for automation and content throughput.

#### Risk areas to manage early

- **IP contamination:** Only use models with known training sources or enterprise licenses; keep a clean-room path for key assets.
- **Licensing clarity:** Lock down license terms for commercial use, redistribution, dataset ownership, and derivative rights.
- **Player trust and ratings:** Content filters, localization QA, and disclosure policies for stores and ratings boards.
- **Security and privacy:** No sensitive data in prompts; use VPC or on-prem inference for confidential work.

#### Team skills to prioritize

- **Art + design:** Prompt systems, reference curation, iterative direction, and style consistency checks.
- **Engineering:** Model APIs, eval harnesses, caching, batch jobs, and observability for AI features in production.
- **Ops/legal:** Data governance, asset provenance, licensing workflows, and audit trails.

#### Benchmarks that matter

- **Throughput:** Assets per week per seat, dialog minutes per day, code modules per sprint.
- **Quality:** Rework rate, art direction acceptance on first pass, bug density of AI-assisted code.
- **Speed:** Time-to-first-playable, time-to-vertical-slice, iteration cycle time on levels and characters.
- **Cost:** Inference spend per shipped asset, GPU hours per milestone, license fees vs. outsource savings.

#### Context and source

The findings come from CESA, the organizer of Tokyo Game Show. For background on the association, see [CESA (Computer Entertainment Supplier's Association)](https://www.cesa.or.jp/english/?ref=completeaitraining.com). You can also visit the [Tokyo Game Show site](https://tgs.cesa.or.jp/en/?ref=completeaitraining.com) for industry updates.

#### Upskilling for your team

If you're formalizing AI roles and workflows, structured training helps. See the [AI Certification for Coding](https://completeaitraining.com/certification/12b-ai-certification-for-coding/) and the [latest AI courses](https://completeaitraining.com/latest-ai-courses/) for engineers and technical artists.

#### Bottom line

With over half of Japanese studios using generative AI and a third applying it to engine work, AI is now a core production tool, not a side experiment. The teams that win will pair speed with governance: clear policies, strong review gates, measurable KPIs, and focused skill development.

---

This is the Markdown form of https://completeaitraining.com/news/51-of-japanese-game-studios-now-use-generative-ai-32/. The whole site is mapped at https://completeaitraining.com/llms.txt.
