Contribute to Defold

Defold is developed in the open by the Defold Foundation together with community contributors. You can help improve the engine, editor, extensions, documentation, tutorials, and examples.

Start by choosing an area, reading the contribution guidelines, and keep each change focused, tested, and easy to review.

I want to help! Contribution Guidelines ↗

Choose where to contribute

You can contribute not only to the engine or editor source code - there are manuals, examples, tutorials and documentations that we;d love to get a glow up, or translation to your native language! Pick the repository that matches the kind of improvement you want to make.

Core source code and tooling

Work on the runtime, editor, platform integrations, and infrastructure that supports native extension builds.

Engine and editor

The main Defold repository for runtime code, editor work, platform support, build flow, and core engine systems. Check details in the repository. ↗

Extension build server

Improve the build service and tooling used to compile native extensions for Defold projects. Check details in the repository. ↗

Documentation and learning content

Improve the learning materials that help new and returning users understand Defold faster.

Manuals and tutorials

Update the documentation source for manuals, tutorials, and learning content published on the Defold site. Check details in the repository. ↗

Examples

Improve example projects and sample code that show Defold concepts in small, practical use cases. Check details in the repository. ↗

What good contributions look like?

Before opening a pull request, make sure the change is scoped clearly, validated properly, and aligned with existing Defold patterns.

Bug fixes

Fix one well-defined problem at a time and make it easy for reviewers to confirm the behavior change.

Keep the contribution focused on a single bug or regression.
Add or update unit tests when the change should be covered by tests.
Test on all affected platforms when the bug is platform-specific.
Follow existing code style and implementation patterns.
Make sure you are legally entitled to submit the work.

New features

New functionality should be intentionally scoped, well designed, and justified by a real Defold use case.

Keep the contribution to one clear feature or capability.
Confirm the design fits Defold’s existing architecture and workflows.
Add tests and validate the feature on all affected platforms.
Follow existing code style and implementation patterns.
Make sure you are legally entitled to submit the work.

Before you open a pull request

Use the official guide and the public discussion channels before investing in a large change. That reduces review churn and helps align the work with how Defold is maintained.

Contribution Guidelines ↗ Code of Conduct ↗ Source code forum ↗ How to report issues?

Other ways to help

If you are not ready to submit code or docs yet, you can still help Defold by reporting issues clearly, helping other developers, or supporting the Foundation.