# Port an Unreal game and leave the royalty behind > Porting an Unreal game means rebuilding a project you own. Blueprints and uasset files do not convert, so the rebuild uses your source art and your logic. - URL: https://www.summerengine.com/port-an-unreal-game - Keyword: port an unreal game - Related: https://www.summerengine.com/porting Porting an Unreal Engine game means rebuilding a project you own in another engine. Blueprint graphs cannot be exported to another engine. Uasset and umap files are Unreal specific containers. There is no converter, and any tool claiming to translate a full Unreal project is not doing what the name implies. What transfers is your source content. FBX models, texture files, audio, and animation exports are standard formats. Your C++ gameplay code documents your systems precisely. Your level layouts and tuning values transfer as data even when the files do not. Epic charges a royalty on gross revenue above a threshold for games shipped with Unreal. Summer Engine charges no royalties at all, and you own the project. It is compatible with Godot 4 workflows, follows Godot upstream, and is a fully custom engine with more than a million lines of custom code. ## Actors, components, and Blueprints in a scene tree An Actor with components becomes a node with child nodes and a script. A Blueprint class becomes a reusable scene plus a script. BeginPlay becomes a ready callback and Tick becomes a per frame process callback. Character Movement Component has no one to one equivalent, so plan to rebuild the movement model explicitly. Blueprint visual graphs have to be read and reimplemented, which is why teams with heavy Blueprint logic should budget more time than teams with C++ gameplay code. ## Materials, Nanite, and Lumen need re-authoring Unreal material graphs do not export. They are reimplemented as shaders, and most of them are simpler than they look once you strip Unreal specific nodes. Nanite geometry and Lumen global illumination are engine features, not asset formats, so content authored to rely on them needs conventional handling: proper LODs, baked or realtime lighting suited to the target platform, and an art pass on anything that depended on unlimited triangle budgets. This is the largest technical item in most Unreal ports. ## Why teams leave Unreal for a port The common reasons are concrete. Project size and build times on mid range hardware. Shipping to mobile, where an Unreal build is heavy. The royalty on revenue above the threshold. Wanting a smaller runtime for a 2D or stylized game that never needed a film grade renderer. If none of those apply to you, staying in Unreal may be the right call. A port is a rebuild and it costs real time. ## Keeping the asset pipeline you already have Your DCC pipeline barely changes. Models exported as FBX or glTF, PBR texture sets, and animation clips all import directly. Keep your naming conventions and folder structure so the rebuilt project stays navigable to the same team. Summer Engine can generate the initial scene structure and gameplay scripts from a description of your existing systems, so you correct a working draft instead of rebuilding from an empty project. ## FAQ ### Can Blueprints be converted to another engine? No. Blueprint graphs are Unreal specific and have no export path to other engines. They must be read and reimplemented as scripts. Unreal C++ gameplay code is easier to work from, since the logic is already written out. ### Can uasset files be imported? No. Uasset and umap files are Unreal container formats. Export your content from Unreal or, better, use the original source files: FBX or glTF models, PBR texture sets, audio files, and animation clips. Those import directly. ### What happens to Nanite and Lumen content? Both are engine features rather than asset formats, so content built to depend on them needs re-authoring. That means proper LODs for geometry that relied on Nanite and a lighting approach suited to the target platform in place of Lumen. ### Does porting away from Unreal remove the royalty? A game built and shipped in Summer Engine has no royalty and no revenue share, and you own the project. Terms for anything you previously shipped with Unreal are governed by the agreement you accepted for that product, so check it for the original release. ### Is porting from Unreal worth it? It depends on why you are moving. Concrete reasons are build times, mobile targets where Unreal builds are heavy, runtime size for stylized or 2D games, and the royalty. If none of those apply, staying in Unreal may be the better decision, because a port is a real rebuild. [Rebuild your Unreal game](https://www.summerengine.com/download) --- ## Machine-readable resources - Site index for agents: https://www.summerengine.com/llms.txt - Full inlined content: https://www.summerengine.com/llms-full.txt - Porting catalog: https://www.summerengine.com/llms-porting.txt - Structured catalog: https://www.summerengine.com/agent-catalog.json - Sitemap: https://www.summerengine.com/sitemap.xml - Developer resources: https://www.summerengine.com/docs