For Unreal developers
Unreal Engine HTML5 export, what happened and what works now
The HTML5 target left the engine years ago, and Unreal Engine 5 never had one. Here is what the community extension and Pixel Streaming can do, what each costs you, and why most teams build a smaller web version instead.
The short answer
As of Unreal Engine 4.24, Epic moved HTML5 support out of the engine to a public Platform Extension maintained by the community, and Unreal Engine 5 has no HTML5 or WebGL export from Epic. Community forks keep Unreal Engine 4.24 and 4.27 running in WebGL, with caveats and Windows-only packaging. Epic's browser answer for Unreal Engine 5 is Pixel Streaming, which runs the game on a server GPU and streams video to the browser, so cost grows with every concurrent player. For a public web game, the realistic path is a smaller web-first version built in a web-capable engine. Summer does not export to the web today and is not a fix for this.
Search for Unreal Engine HTML5 export and you will find tutorials from the Unreal Engine 4 era, forum threads asking where the option went, and plugins that promise a way back. The short version is that Epic stopped shipping an HTML5 target with Unreal Engine 4.24, moved it to a community-maintained extension, and never added one to Unreal Engine 5.
That leaves three real options. Stay on an older Unreal Engine 4 with a community fork, stream the game from a server with Pixel Streaming, or build a web version in a tool made for the browser. Each fits a different goal, and the right one depends on whether the web version is a demo, a showroom or a game that has to earn its own players on a portal.
What it does
The Unreal Engine 4 community extension
Epic's own documentation says that as of Unreal Engine 4.24, HTML5 support was migrated out of the engine to a public Platform Extension that community members can maintain and improve. The UnrealEngineHTML5 organization on GitHub describes itself as a community-supported HTML5 platform extension for Unreal Engine 4.
Community forks for 4.24 and 4.27
The SpeculativeCoder fork targets Unreal Engine 4.27 with WebGL 2 and 4.24 with WebGL 1. Its README says it works best in Firefox or Chrome on Windows, that development and packaging happen on Windows only, and that there are a number of caveats to read first.
Access through your Epic account
Like the engine source, these forks are only visible after you link your GitHub account to your Epic Games account. Until then the repositories answer with a 404.
Pixel Streaming in Unreal Engine 5
Pixel Streaming runs a packaged Unreal application on a desktop PC or a cloud server and streams the rendered frames and audio to a browser over WebRTC, with keyboard, mouse, touch and gamepad input sent back.
One instance per player
For separate sessions, Epic's hosting guide says your scaling solution should provision a new Unreal Engine instance whenever a user connects. Every concurrent player is a running copy of your game on a GPU you pay for.
A web-first version
A smaller game built for the browser in a web-capable engine, sized for portal budgets, often does more for an Unreal project than a port. It can act as the demo that sends players to the Steam page of the full game.
How it works
- 1
Step 1: Decide what the web version is for
A playable teaser, an architectural or product showroom, a playtest link for a few testers, and a free game that has to find players on a portal are different problems. Write down which one you have before choosing a route.
- 2
Step 2: If you must stay in Unreal Engine 4, test a community fork
Link your GitHub and Epic accounts, read the fork's caveats, and package a small test map on Windows. Measure the download size and load time in Chrome and Firefox before you commit a real project, and plan on staying on that engine version.
- 3
Step 3: If a few people need the full game in a browser, price Pixel Streaming
Stand up one streaming instance on a GPU server and test latency from where your users are. Then multiply by the number of players you expect at the same time, because each separate session needs its own instance. Consumer GPUs often limit hardware H.264 encoding to eight sessions.
- 4
Step 4: For a public web game, scope a web-first slice
Pick one level, mode or mechanic that shows what the game is about and can fit a portal budget. CrazyGames wants an initial download of 50 MB or less, and 20 MB or less for its mobile homepage, and YouTube Playables caps the initial bundle under 30 MiB.
- 5
Step 5: Build it in a web-capable engine and reuse what you can
Stock Godot 4 with GDScript, three.js or Phaser all target the browser directly. Export meshes from your Unreal project where your licenses allow, rebuild materials for the new engine, and rewrite gameplay, since Blueprints and C++ do not carry over. Check the license of every marketplace asset before using it outside Unreal.
- 6
Step 6: Point the web version at the full game
End the web slice with a clear link to the Steam page and a wishlist prompt. The browser version finds players cheaply, and the Unreal build stays the product.
Two ways to run it
In Studio, or from the agent you already use
In Summer Studio
Summer Studio runs in the browser and generates assets you can use in any engine, including a web-first slice. Generate low-poly 3D models as GLB files with a polycount target, textures and 2D art, sound effects and music, then download them. Studio does not export or host games.
Open the 3D tab in StudioFrom Claude, Cursor or Codex via MCP
From Claude Code, Cursor or Codex, the Summer MCP can generate assets for your web slice with summer_generate_3d, summer_generate_image and summer_generate_audio. These run on Summer's servers without the Summer app open, and your agent saves the files into the web project. Summer's engine does not build the web version.
Example prompt for your agent
Generate three low poly props for my web demo with Summer, a wooden crate, a stone pillar and a lantern, each under 10K faces, then give me the download links and save the GLB files into public/models.Set up the Summer MCP
| Route | Engine version | What the player downloads | Main cost |
|---|---|---|---|
| Community HTML5 extension or fork | Unreal Engine 4.24 or 4.27 | The WebGL build of your game | Staying on Unreal Engine 4, Windows-only packaging, community support only |
| Pixel Streaming | Unreal Engine 5 | A video stream over WebRTC | A GPU server instance for each concurrent session, plus latency |
| Web-first slice in a web-capable engine | Any, the slice is rebuilt | A small web build sized for portals | Rebuilding gameplay for a second, smaller game |
| No web version, a Steam demo instead | Any | A desktop demo | Players must install it |
Sources: Unreal Engine 4.26 docs, HTML5 Game Development (archived)
Examples
Prompts that work, and what comes back
Checks and prompts for deciding and building the web version of an Unreal game.
Route decision
Prompt
Checklist. Who plays it, how many at once, from where, on which devices, and does it need to earn players on a portal or only support the main game?
What you get
A clear pick between a community fork, Pixel Streaming and a web-first slice.
Pixel Streaming cost model
Prompt
Checklist. Peak concurrent players times hours per day times the hourly price of one GPU instance in your cloud, plus bandwidth.
What you get
A monthly estimate from your own cloud prices, which shows quickly whether streaming fits a free game or only a paid showroom.
Web slice scope
Prompt
List the smallest set of levels, enemies and systems that shows the core loop in under ten minutes of play, with a budget of 20 MB before gameplay.
What you get
A scope for the web version that fits the strictest portal you target.
Asset reuse audit
Prompt
Checklist. For every mesh, texture and sound, note where it came from, whether its license allows use outside Unreal, and its size after compression.
What you get
A list of assets you can export to the web version and those you need to replace.
Replacement props
Prompt
Low poly stone archway, mossy, 8K faces, stylized hand-painted texture
What you get
A GLB from Studio that fits a web budget, to replace a heavy or Unreal-only asset in the web slice.
What happened to HTML5 in Unreal Engine
Unreal Engine 4 shipped an HTML5 target for years. Epic's documentation for 4.26 opens with the change. As of Unreal Engine 4.24, support for the HTML5 platform was migrated out of the engine to a public Platform Extension that can be maintained and improved by community members, with its documentation hosted alongside the GitHub repository.
The community extension and the best-known fork both target Unreal Engine 4. Unreal Engine 5 has no HTML5 target from Epic, and Epic's route to the browser for Unreal Engine 5 projects is Pixel Streaming. If you see a tool claiming one-click Unreal Engine 5 web export, treat it as a third-party product and test it on your own project before relying on it.
Pixel Streaming, and why cost scales with players
Pixel Streaming does not put your game in the browser. The game runs on a machine with a GPU, and the browser shows a video of it and sends input back. That keeps the full quality of your packaged game, and the player's device only has to decode video, which is why it suits showrooms, configurators and demos for a known audience.
The catch is scale. Several viewers can watch one session, but separate sessions each need their own instance, and Epic's guide says a scaling solution should provision a new instance whenever a user connects. Epic deprecated its matchmaker in Unreal Engine 5.5 and says a ready-made scaling solution is outside what it provides. For a free game on the open web, a GPU per concurrent player rarely pays for itself.
The realistic web path
Most Unreal teams who want web players end up building a second, smaller game. It is not a port, it is a web-first version designed around the browser's limits, with a small first download, simple lighting and a short session. Portals publish strict budgets, so measure any WebGL build of a full Unreal game against them before you commit.
Pick an engine that targets the web directly. Stock Godot 4 with GDScript exports single-threaded web builds by default since 4.3, three.js suits code-first 3D in the page, and Phaser suits 2D. Keep the Unreal project as the full game on Steam and consoles, and let the web version bring players to it.
Where Summer fits
Summer does not export to the web today. Web export is not available in Summer yet, so it is not a fix for Unreal's missing HTML5 target. Summer is a desktop engine for macOS and Windows, compatible with Godot 4, that builds Windows and macOS games for Steam and itch.io downloads. If you are thinking about moving a desktop game off Unreal for other reasons, the Unreal to Godot guide covers that. For the web version itself, Summer Studio can still make the lightweight assets it needs.
Where to take your Unreal game next
Port it to make money
Steam is where an Unreal game earns, with a desktop build and no browser needed. Steam charges a Steam Direct fee of 100 US dollars per game, paid back after the game earns 1,000 US dollars in adjusted gross revenue, and the store page must be visible as Coming Soon for at least two weeks before release.
How to publish a game on SteamRelease it on Summer Games
Summer Games is a new store for games made with Summer. It is launching soon. An Unreal build will not qualify. A game built in Summer, reviewed, and working as a single-player game first is the kind that will be ready.
See Summer Games (launching soon)Grow it
Use the web slice as marketing. Put it on a portal, end it with a link to the Steam page, and pair it with a store page that is live early, a trailer that shows play in the first seconds, and creators who cover your genre.
Market your indie gameRemake it in Summer
If you want a lighter desktop version outside Unreal, start from a Summer template near your genre, bring in the assets your licenses allow, and have the agent rebuild each system with your Blueprints and design notes as the spec. Playtest in the engine as you go.
Remake your game in SummerFrequently asked questions
Can Unreal Engine 5 export to HTML5?
Not from Epic. HTML5 support left the engine with Unreal Engine 4.24 as a community-maintained extension, and Unreal Engine 5 has no HTML5 or WebGL target. Epic's browser route for Unreal Engine 5 is Pixel Streaming, which streams video from a server.
When did Unreal remove HTML5 export?
With Unreal Engine 4.24. Epic's documentation says that as of that version, HTML5 support was migrated out of the engine to a public Platform Extension that community members can maintain and improve.
Is there an Unreal Engine HTML5 plugin on GitHub?
There are community forks on GitHub for Unreal Engine 4, such as one that targets 4.27 with WebGL 2 and 4.24 with WebGL 1, and the UnrealEngineHTML5 organization hosts the community extension. They require linking your GitHub and Epic accounts, package on Windows only, and come with caveats. None is supported by Epic.
Is Pixel Streaming the same as a web export?
No. With Pixel Streaming the game runs on a server or desktop PC with a GPU and the browser receives video and audio over WebRTC. The player downloads no game files, and you pay for a running instance per separate session.
How much does Pixel Streaming cost?
Epic does not set a price, because you host it. The cost is your cloud's hourly price for a GPU instance, times the number of concurrent sessions, times the hours they run, plus bandwidth. Epic's guide says scaling should start a new instance whenever a user connects.
What is the best way to make a web version of my Unreal game?
Build a smaller web-first version in an engine that targets the browser, such as stock Godot 4 with GDScript, three.js or Phaser, and size it for portal budgets. Use it to send players to the full game on Steam.
Can Summer export my Unreal game to the web?
No. Summer does not export to the web today, and it does not import Unreal projects. Summer builds desktop games for macOS and Windows. Studio can generate lightweight models, art and audio for a web version you build elsewhere.
Related tools and guides
Sources
- Unreal Engine 4.26 docs, HTML5 Game Development (archived 2022)
- UnrealEngineHTML5 on GitHub
- UnrealEngineHTML5 documentation
- SpeculativeCoder, UnrealEngine-HTML5-ES3
- Epic forum, HTML5 in UE4 and UE5 (2021 thread quoting the docs)
- Unreal Engine docs, Pixel Streaming
- Unreal Engine docs, Hosting and networking guide for Pixel Streaming
- CrazyGames technical requirements
- YouTube Playables stability and performance requirements
- Godot docs, Exporting for the Web
- Steamworks, Steam Direct fee
- Steamworks, Coming Soon page
Make your game. Grow your game.
Even if it is built in another engine.
Free to download for macOS (Apple silicon) and Windows.