# Cesium for Unreal puts a WGS84 globe and 3D Tiles inside the editor > Cesium for Unreal is an Apache 2.0 Unreal Engine plugin that combines a full scale WGS84 globe, the 3D Tiles open standard and Cesium ion content with the engine's own physics, collision and landscaping tools. The plugin is free, the content behind it is not, and the plugin version follows the engine version closely. **CesiumGS/cesium-unreal** — Bringing the 3D geospatial ecosystem to Unreal Engine - Repository: https://github.com/CesiumGS/cesium-unreal - Website: https://cesium.com/platform/cesium-for-unreal/ - Stars: 1,249 · Forks: 380 - Language: C++ - License: Apache-2.0 - Published: 2026-10-19 · Updated: 2026-10-19 · Language: en - Canonical page: https://hysenlabs.com/projects/cesiumgs-cesium-unreal ## A globe with a coordinate system, not a terrain tile Cesium for Unreal brings the 3D geospatial ecosystem to Unreal Engine, and the components it combines matter. The first is a high accuracy full scale WGS84 globe, which is not the same thing as a large terrain heightmap. A globe means the world has a defined coordinate system and a curvature, so a kilometre means the same distance everywhere on the surface, which is exactly what a flight simulator, a city planning tool or a defence simulation needs and what a flat plane approximation cannot give. The second component is the open standards and open APIs for spatial indexing, 3D Tiles in particular, which is the format for streaming very large amounts of geometric detail such as photogrammetry, terrain, imagery and 3D buildings. The third is cloud based real world content from Cesium ion, and the project is explicit that this content is available as optional commercial subscriptions. The engine integration is where the plugin becomes more than a viewer. The documentation states that Cesium for Unreal is tightly integrated with Unreal Engine, which makes it possible to visualize and interact with real world content in the editor and at runtime, and that the plugin also has support for Unreal Engine physics, collisions, character interaction and landscaping tools. That is the decisive difference for a simulation. A viewer that draws a globe gives you a picture. A plugin that registers tiles with the engine's collision and physics systems gives you a character that can walk on a real building and fall down a real slope. The audience is geospatial simulation teams: architects and civil engineers doing site visualisation, defence and emergency planners, and anyone who has to put a real place inside an Unreal scene. ## Content comes from open standards, from ion, or from your own servers The content story has three layers, and the plugin is deliberately not tied to one of them. The first is Cesium ion, which the project describes as integrated into the plugin for instant access to global high resolution 3D content ready for runtime streaming. Ion users can also use cloud based 3D tiling pipelines to create end to end workflows that transform massive heterogeneous content into semantically rich 3D Tiles, ready to stream to Unreal Engine. That is the part that costs money, and the README says so directly, describing the ion content and the tiling pipelines as available as optional commercial subscriptions, and noting that using Cesium ion helps support the development of the plugin. The second is your own data. The project states that the plugin supports cloud and private network content and services based on open standards and APIs, and that you are free to use any combination of supported content sources, standards and APIs with the plugin. For a team with its own imagery, its own photogrammetry or a classified data set, that is the only workable route anyway, and the plugin does not require it to go through a hosted service. The third is the open standard itself. 3D Tiles is a published format, and a project that can produce 3D Tiles is not locked into this plugin. That is worth remembering when the commercial content tier is not an option, and it is also why the plugin is a reasonable thing to fork, since the Apache 2.0 licence lets you take the code and adapt it. There is a community forum for questions, a separate cesium-unreal-samples repository with featured demos, and the user and contributor documentation is hosted at cesium.com. ## Installing: a ZIP in the plugins directory, or the Marketplace The easiest route is the officially released version from the Unreal Engine Marketplace, and the documentation calls that the easiest way to install. The alternative is the Releases page on the repository, which the README recommends if you want an older version, or if you cannot or do not want to use the Marketplace, and it points out that on Linux the Releases page is the better option. The install itself is a file operation rather than a command, and the documentation describes it in three steps. If you previously installed the plugin through the Marketplace, uninstall it first, because you should not have two copies. Then extract the release ZIP into the engine's Engine/Plugins/Marketplace directory, creating that directory if it does not exist. On Unreal Engine 5.6 on Windows that path is typically C:\Program Files\Epic Games\UE_5.6\Engine\Plugins\Marketplace. If you have done this correctly you will find a CesiumForUnreal sub-directory inside the Marketplace directory, and the plugin is ready to use. The verification step is the useful part of that instruction, because the failure mode of this kind of install is silent: a plugin in the wrong directory simply does not appear in the editor, and the beginner spends an hour looking for a menu item that is not there. After installation, the Quickstart tutorial is the place to go next, since it covers the first use with real content. There is also a separate page on using pre-release packages for those who want to test a build ahead of a release. ## The plugin is a native C++ project with a build of its own The repository is a full Unreal Engine plugin source tree, and the layout shows it. CesiumForUnreal.uplugin is the plugin descriptor, Source holds the C++ implementation, Shaders holds the rendering side, Config the plugin settings, Content the assets, and Documentation the user and contributor guides, with a Doxyfile for generating reference documentation. There is a TestsProject for exercising the plugin, a ThirdParty.json describing the bundled dependencies, an extern directory for vendored code, and scripts including a release-prep script. The package.json is unusual for an Unreal plugin and tells you something about the tooling. It is marked private, so it is not published to npm, it names the project @cesium/cesium-unreal, and it carries three scripts: format runs clang-format over the C++ sources under Source, doxygen runs the Doxyfile to build the reference docs, and release-prep runs node scripts/release-prep.js. The devDependencies are just clang-format and doxygen-awesome-css. In other words, the JavaScript in this repository is a small tooling layer around a C++ codebase, and the formatting and documentation rules are enforced through it. One detail is worth flagging for anyone tracking versions. The version field in package.json reads 2.28.0, while the most recent published plugin release is v2.30.0. The root package version and the release tag are therefore not kept in lockstep in the tree, which means the number in the file is not a reliable way to tell what you have installed. The release tag is. For anyone who wants to modify the plugin, the Developer Setup Guide in the Documentation directory covers setting up an environment to compile it, customise it and contribute back. ## The plugin version follows the engine version, and that is a constraint The support policy is stated in one sentence: Cesium for Unreal supports the three most recent versions of Unreal Engine. Older versions of the plugin may be used with older versions of the engine, but the project recommends staying up to date if at all possible. The consequence shows up in the table of last supported releases. Unreal 4.26 is at v1.20.1, 4.27 at v1.24.0, 5.0 at v1.31.1, 5.1 at v2.5.0, 5.2 at v2.11.0, 5.3 at v2.17.0, 5.4 at v2.21.1 and 5.5 at v2.28.0. Each engine generation maps to a specific plugin release, and each of those tags is named with a -ue4 suffix where it belongs to the older branch. This is a real planning constraint for a studio. A team that upgrades Unreal to a new version has to take a matching plugin release, and a team pinned to an older engine for a shipped product is pinned to a plugin version that no longer receives the newest work. The current release line is healthy, with v2.29.0 on 2026-08-03, v2.29.1 on 2026-09-01 and v2.30.0 on 2026-09-29, and the last push to the repository was on 2026-10-19. The CHANGES.md file at the root is the changelog to read before each upgrade, and the documentation links to a changes page as part of the reference documentation. For a plugin that sits under the geometry of a simulation, an upgrade that changes collision or tiling behaviour is worth reading about rather than discovering. ## Where the money is: the plugin is free, the content is not The licensing picture is unusually clean and unusually important. The plugin is Apache 2.0, and the README states that Cesium for Unreal is free for both commercial and non-commercial use. The package metadata agrees, listing the licence as Apache-2.0 and the author as CesiumGS, Inc. and Contributors. The CODE_OF_CONDUCT.md and CONTRIBUTING.md at the root confirm it is run as a normal open source project with a community process. The content is a separate commercial relationship. The real world 3D content and the cloud based tiling pipelines that prepare your own data into streamable 3D Tiles are described as optional commercial subscriptions from Cesium ion. That is the honest dividing line: the engine integration, the globe, the standards support and the plugin code are free, and the curated global content and the hosted processing pipeline are the paid part. The licence terms also decide what you may do with the plugin itself. Apache 2.0 permits use in commercial products, modification and redistribution with the notice preserved, and it carries an explicit patent grant, which is a meaningful protection for a plugin you intend to embed in a product. It is also a permissive licence, so there is no requirement to contribute your changes back, although the project has a public contributor process and the Developer Setup Guide is written for exactly that. For a team that wants the plugin but not the hosted content, the Apache 2.0 terms make the path open, since the project states you are free to use any combination of supported content sources, standards and APIs. ## The alternative: build your own 3D Tiles integration There is a genuine alternative, and it is worth describing precisely because the difference is about how much you take on. The alternative is to write your own Unreal Engine plugin against the 3D Tiles standard and point it at your own data. You would handle the tile streaming, the geometric decoding, the coordinate transformation from geographic to engine space, and the integration of the resulting geometry with the engine's collision and physics systems, which is the hardest part of the job and the part that decides whether a character can actually stand on the terrain you loaded. You would also own the maintenance of that code against every engine upgrade. Cesium for Unreal exists so that you do not have to. It ships the globe, the standards support, the engine integration with physics, collisions, character interaction and landscaping, the ion integration for ready made content, and a path to the hosted tiling pipeline for turning your own captured data into 3D Tiles. What you give up is control of the internals, and you accept the engine version window described above. A third option is to leave Unreal out of it. If your requirement is accurate global terrain and imagery with your own camera and interaction model, a web or native 3D Tiles viewer written directly against the standard will do the job with no engine at all, and it will not be tied to the Unreal release cycle. That is the right answer when the output is a viewer. It is the wrong answer when the output is a simulation, because the moment characters, vehicles or physics have to interact with the real world geometry, you are back to building the engine integration. The decision therefore comes down to the interaction, not the imagery. If you need to drive a vehicle across a real terrain, the plugin is cheaper than writing the integration. If you need to fly a camera over it, the alternative is cheaper. ## Conclusion Cesium for Unreal is worth adopting when a simulation or application has to sit on real world terrain and buildings, and your team would rather not build a 3D Tiles renderer and an Unreal integration from scratch. It is the wrong choice if the world you need is entirely synthetic, if you cannot rely on network access to the content source, or if your content is licensed from elsewhere and streaming it is not on the table. Before you install it, read the Quickstart tutorial, confirm your engine version against the support policy of the three most recent Unreal versions, and check where the content comes from, because the plugin code is Apache 2.0 and free for commercial use while the Cesium ion content and cloud tiling pipelines are described as optional commercial subscriptions. ## FAQ ### What does Cesium for Unreal actually add to Unreal Engine? It combines a high accuracy full scale WGS84 globe, open standards and APIs for spatial indexing such as 3D Tiles, and cloud based real world content from Cesium ion, and it integrates that with Unreal Engine physics, collisions, character interaction and landscaping tools so the content can be used in the editor and at runtime. ### How do I install the Cesium for Unreal plugin? The easiest way is the Unreal Engine Marketplace, and on Linux the README suggests using the Releases page instead. Extract the release ZIP into the engine's Engine/Plugins/Marketplace directory, create that directory if needed, and confirm you now have a CesiumForUnreal sub-directory inside it. Uninstall any previous Marketplace copy first. ### Which Unreal Engine versions does Cesium for Unreal support? The project supports the three most recent versions of Unreal Engine, and the README lists the last plugin release for older versions, from v1.20.1 for Unreal 4.26 up to v2.28.0 for Unreal 5.5. The project recommends staying up to date where possible. ### Is Cesium for Unreal free to use commercially? The plugin is released under Apache 2.0 and the README states it is free for both commercial and non-commercial use. The real world content and the cloud based 3D tiling pipelines from Cesium ion are described separately as optional commercial subscriptions. ### Can I use my own 3D Tiles content with the plugin? Yes. The project states that the plugin supports cloud and private network content and services based on open standards and APIs, and that you are free to use any combination of supported content sources, standards and APIs. Cesium ion users can additionally use the cloud based 3D tiling pipelines to turn their own data into streamable 3D Tiles. ## Sources - [CesiumGS/cesium-unreal on GitHub](https://github.com/CesiumGS/cesium-unreal) - [License: Apache-2.0](https://github.com/CesiumGS/cesium-unreal/blob/main/LICENSE) - [Project website](https://cesium.com/platform/cesium-for-unreal/) - [README](https://github.com/CesiumGS/cesium-unreal/blob/main/README.md) - [Releases](https://github.com/CesiumGS/cesium-unreal/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/cesiumgs-cesium-unreal