Contributing to LVGL

Thank you for considering contributing to LVGL. If you have some spare time to spend with programming you will certainly find a way to helpimproving LVGL. Do not afraid to take the first step! Everybody is welcome independently from gender, age, color, location, or skill level. So don’t be shy, pick a point from the list below that you are interested in, and let’s go! :rocket:


There are many ways to join the community. If you have some time to work with us you will surely find something that fits you! You can:

We have some simple rules:

How to send a pull request?

Merging new code into LVGL, documentation, blog, and examples happens via Pull requests. If you are still not familiar with Pull Requests (PR for short) here is a short guide. It’s about the lvgl repository but it works the same way for other repositories too.

  1. Fork the lvgl repository. To do this click the “Fork” button in the top right corner. It will “copy” the lvgl repository to your GitHub account (
  2. Clone the forked repository and add your changes
  3. Create a PR on GitHub from the page of your lvgl repository ( by hitting the “New pull request” button
  4. Set the base branch. It means where you want to merge your update. Fixes go to master, new features to feature branch.
  5. Describe what is in the update. An example code is welcome if applicable.
  6. Update your lvgl branch with new commits. They will appear in the PR too.

Some advice:

Help others in the Forum

It’s a great way to contribute to the library if you already use it. Just go to a register (Google and GitHub login also works). Log in, read the titles and if you are already familiar with a topic, don’t be shy, and write your suggestion.

Improve or translate the documentation

If you would like to contribute to LVGL the documentation is the best place to start.

Fix typos, add missing parts

If you find a typo, an obscure sentence or something which is not explained well enough in the English documentation click the “Edit on GitHub” button in the top right corner and fix the issue by sending a Pull Request.

Translate the documentation

If you have time and interest you can translate the documentation to your native language or any language you speak well. You can join others to work on an already existing language or you can start a new one.

To translate the documentation we use Zanata which is an online translation platform. You will find the LVGL project here: LVGL on Zanata

To get started you need to:

Note that a translation will be added to the documentation only if the following parts are translated:

Write a blog post

Have you ported LVGL to a new platform or created a fancy GUI? Do you know a great trick? You can share your knowledge on LVGL’s blog! It’s super easy to add your own post:

The blog uses Jekyll to convert the .md files to a webpage. You can easily run Jekyll offline to check your post before creating the Pull request

Report or fix bugs

For simple bugfixes (typos, missing error handling, fixing a warning) it’s fine to send a Pull request directly. However, for more complex bugs it’s better to open an issue first. In the issue, you should describe how to reproduce the bug and add the minimal code snippet.

Suggest or implement new features

If you have a good idea don’t hesitate to share with us. It’s even better if you have time to deal with its implementation. Don’t be afraid if you still don’t know LVGL well enough. We will help you to get started.

To share your ideas use Feature request category of the forum.

If you are ready to get involved into the development of this faetures feel free to pen a new issue for it on GitHub.

During the implementation don’t forget the Code style guide.

If you implemented a new feature it’s important to record it in the documentation and if applicable create an example for it:


I hope you have taken a liking to contribute to LVGL. A helpful and friendly community is waiting for you! :)