AI NPCs for Unity WebGL and Browser Games - What Works in 2026

Browser games are the fastest way to get a game in front of players: no install, one link. They are also where AI NPCs most often break, because Unity does not support the Microphone class in WebGL builds.

Here is what works in the browser as of October 2026.

Quick comparison

The WebGL microphone problem

Browsers handle microphone access themselves, behind a permission prompt, and Unity's built-in Microphone API does not work in WebGL. Any AI NPC tool that relies on it will work in the Editor and fail in your browser build.

Neocortex solves this with a WebGL template that bridges the browser's audio to Unity. You switch your build to the Neocortex WebGL template, and the same voice components you use on desktop work in the browser. We wrote about how it works.

What to check before you ship a browser build

• HTTPS. Browsers only allow microphone access on secure pages.
• A user gesture. Microphones start after the player clicks or taps.
• Your API key. Never ship a secret key in a WebGL build, where anyone can read it.
• Build size. Local models are rarely practical in the browser, so cloud inference is the norm.

Why browser game developers choose Neocortex

Voice that works in WebGL. Microphone input and streamed voice replies in the browser.

One character everywhere. The same character runs in your WebGL build, your desktop build and through the Web API in any web stack.

Designers own the character. Personality, emotion, knowledge, intents and actions are designed visually and tested in the browser.

Tool details were last checked in October 2026.