You cannot combine Unreal Engine with open-source code licensed under GPL, LGPL, or similar copyleft licenses. This restricts how you can integrate certain widely-used open-source libraries into Unreal Engine projects.
This analysis describes what Unreal Engine's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
Many developers routinely use GPL or LGPL-licensed open-source libraries, and this restriction may require significant code review and refactoring to ensure compliance in projects that incorporate Unreal Engine.
Developers who use GPL or LGPL open-source libraries in their projects need to carefully audit whether those libraries can be integrated with Unreal Engine under this restriction, as violating it constitutes a license breach.
How other platforms handle this
Do not use our name or logo in ways that could imply an official partnership or endorsement without our permission. This includes not naming your project in a way that could make people think it is an official Minecraft product.
"Content" means anything you or your Customers create or make available through the Service in connection with your Account, including your intellectual property (e.g. trademarks, trade names, service marks, and copyrighted works); the products or services you offer (e.g., courses, coaching, members...
By posting, uploading, inputting, providing or submitting your Content you grant Kit, its affiliated companies and necessary sublicensees permission to use your Content in connection with the operation of their Internet businesses including, without limitation, the rights to: copy, distribute, trans...
Monitoring
Unreal Engine has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 25 platforms.
"You may not, and may not permit others to, combine, Distribute, or otherwise use the Licensed Technology with any code or other content which is covered by a license that would directly or indirectly require that all or part of the Licensed Technology be governed under any terms other than those of this Agreement (those licenses, the 'Non-Compatible Licenses'). This means, for example, that you may not combine the Licensed Technology with code or content that is licensed under any of the following licenses: GNU General Public License (GPL), Lesser GPL (LGPL) (unless you are merely dynamically linking a shared library), or Creative Commons Attribution-ShareAlike License.— Excerpt from Unreal Engine's Unreal Engine EULA
REGULATORY LANDSCAPE: This provision engages copyright law principles around license compatibility, particularly the copyleft mechanism of GPL and LGPL. There is no direct regulatory agency overseeing software license compatibility, but violation of open-source license terms by third-party library authors could independently create copyright infringement exposure. The Linux kernel's LGPL-covered components and their use in game development contexts have historically been subject to significant industry attention. GOVERNANCE EXPOSURE: Medium. The exception for dynamic linking of LGPL libraries is a recognized industry accommodation, but the distinction between static and dynamic linking can be technically nuanced and may require engineering review. Studios that use third-party middleware or plugins should verify the license terms of those components before integrating them into Unreal Engine projects. JURISDICTION FLAGS: Copyright law governing license compatibility applies broadly across jurisdictions, though the specific doctrines around derivative works and copyleft may vary. EU software directive provisions on interoperability may interact with this restriction in complex ways for EU-based developers. CONTRACT AND VENDOR IMPLICATIONS: Middleware and plugin vendors supplying components to Unreal Engine studios should be asked to provide license representations as part of procurement due diligence. Studios that distribute products incorporating third-party open-source components should conduct a software composition analysis to identify any Non-Compatible License exposure before distribution. COMPLIANCE CONSIDERATIONS: Engineering and legal teams should implement a software composition analysis process for all Unreal Engine projects that identifies the license of every third-party dependency. Any GPL or strong copyleft-licensed library should be flagged for review before integration. The dynamic linking exception for LGPL should be confirmed with technical staff on a case-by-case basis.
Full compliance analysis
Regulatory citations, enforcement risk, and due diligence action items.
Free: track 1 platform + weekly digest. Monitor: 25 platforms + same-day alerts. No credit card required.
Buried in Robinhood's customer agreement is broad authority to close your positions, suspend your account, and force arbitration. Here is what it actually says.
Stripe's terms authorize fund reserves, payout withholding, and account termination. Here is what the agreement states and what business owners should review.
Compliance Governance Intelligence
Need to monitor specific governance provisions?
Compliance includes provision-level monitoring, governance timelines, regulatory mapping, and audit-ready analysis.
Built from archived source documents, structured governance mappings, and historical version tracking.
Many developers routinely use GPL or LGPL-licensed open-source libraries, and this restriction may require significant code review and refactoring to ensure compliance in projects that incorporate Unreal Engine.
Developers who use GPL or LGPL open-source libraries in their projects need to carefully audit whether those libraries can be integrated with Unreal Engine under this restriction, as violating it constitutes a license breach.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Unreal Engine.