Start with your distribution
Which Xournal++ Linux download is right?
The Ubuntu and Debian route is familiar to users who prefer packages managed by the operating system. The official project documentation also covers package-manager and distribution-specific choices, so check the guide when your distribution version is different from the release asset shown above. A package can integrate more naturally with menus and file associations, but it may be tied to a particular distribution release.
An AppImage keeps the application in a single bundle. That makes it attractive when you want to test a release without adding a system package, but you still need to make the file executable and decide whether to create a desktop shortcut yourself. Do not treat an AppImage as a replacement for every distribution integration detail.
Flatpak can be a good fit for a desktop that already uses sandboxed applications. The exact permission behavior matters when Xournal++ opens local PDFs or saves notebook files, so keep the document folders accessible and review the official project instructions if a file chooser behaves unexpectedly.
Linux choices
Compare the common Xournal++ installation methods
| Method | Best for | Trade-off |
|---|---|---|
| Ubuntu/Debian .deb | System package and desktop integration | Asset is tied to a distribution family |
| AppImage | A self-contained portable-style bundle | May need executable permission and integration |
| Flatpak | Desktop users already using Flathub | Sandbox permissions may affect file access |
| APT command | Users following distro package instructions | Available version depends on repository state |
Ubuntu and Debian
Install Xournal++ with a package or command
Check the distro
Confirm your Ubuntu or Debian release and CPU architecture before choosing a .deb file.
Choose the route
Use the official package, the project installation guide or the repository command that matches your system.
Launch the app
Open Xournal++ from the application menu and import a PDF or create a blank page.
Test file access
Save a .xopp notebook and export a short PDF to confirm the document folders work.
Troubleshooting
When Linux installation works but the workflow does not
If Xournal++ launches but cannot open a PDF, check file permissions, sandbox restrictions and the folder you selected. If a .xopp file opens without its background, make sure the original PDF is still available at the path saved by the notebook or use an attachment workflow when appropriate.
If a tablet behaves differently after switching package formats, compare the same blank-page test in one installation at a time. Pressure and input behavior can depend on the desktop session, tablet driver and Xournal++ settings, not only on the downloaded package. The stylus guide covers the next checks.
Package choice
Repository package or official release asset?
The command sudo apt install xournalpp is convenient because the package manager handles installation and updates in the way your distribution expects. Its version is controlled by the repository metadata, however, so it may not match the newest project release. That is not automatically a problem: a repository build can be the better choice when system integration and predictable updates matter more than a new feature.
Use the official release asset when you specifically need the release version shown on the download page or when your distribution does not provide a suitable package. Do not add a random personal repository just to make a command succeed. Record which installation method you used, because mixing a package-manager build, an AppImage and a Flatpak can make it difficult to know which copy opened a notebook or which preferences are active.
Desktop integration
Check the file chooser and launcher
Once Xournal++ opens, test the two actions that reveal most Linux packaging problems: choose a PDF from the file chooser and save a small .xopp notebook into a folder you own. If the application is missing from the desktop menu, the package may still work from the command line; desktop integration is a separate packaging detail. If a sandboxed build cannot see a directory, review its documented permissions instead of copying sensitive PDFs into an unknown temporary folder.
Linux package decision
Choose the right Xournal++ Linux download
The Xournal++ Linux download should match both your distribution and the way you want desktop software managed. A .deb package is a familiar choice for Ubuntu or Debian systems and usually fits system menus and package maintenance. An AppImage is more self-contained and can be useful when you want to keep the application in a user-controlled folder, but it may require executable permission and extra desktop integration. Flatpak can provide a sandboxed workflow, so review file access when the notebook or PDF is outside the locations the sandbox can see.
After the Xournal++ Linux download opens, test file selection, PDF background access and saving an .xopp notebook before importing a large study folder. A command such as sudo apt install xournalpp may be appropriate for a repository package, but the available version depends on the distribution. If the launcher is missing, distinguish desktop integration from the application itself. This Xournal++ Linux download guide keeps the package choice visible, explains the permission trade-off and points to the official documentation for commands that depend on a specific release. Keep the downloaded file beside its release notes until the first test is complete.
If you compare more than one Linux download, test each package with the same short PDF and notebook. That simple download check makes it easier to spot differences in file permissions, desktop launchers and PDF access before you move your real notes.
Frequently asked questions
Xournal++ Frequently asked questions
How do I install Xournal++ on Ubuntu?
Use the official Ubuntu or Debian installation path that matches your release. Many users begin with sudo apt install xournalpp, but the available repository version depends on the system.
Is Xournal++ available on Flathub?
The official project documentation lists Flatpak as a Linux installation option. Use the project guide and review permissions when opening local PDFs or saving notebooks.
Should I use the .deb or AppImage?
Choose .deb for system package integration. Choose AppImage when you prefer a self-contained bundle and are comfortable handling executable permission and desktop integration.
Why is my PDF background missing on Linux?
The editable notebook may reference the original PDF path. Keep the background file available or use the .xopp and PDF workflow described in the PDF guide.