Pinta: a .NET 10 app that also installs like a Unix package
Simple GTK Paint Program
At a glance
- What is it?
- A GTK image editor whose quick build is dotnet build on every platform, whose Linux installation path runs autogen.sh and make install with a pkg-config template in the tree, whose Windows dependencies arrive as MSYS2 clang packages with an ARM64 substitution spelled out, and whose privacy statement is a single sentence with an exception clause.
- Who is it for?
- Pick the install route that matches what you are doing, because the project offers two on Linux and they are not equivalent: dotnet run is for development, and only the autotools path honours a prefix and produces the desktop integration files. If you are on macOS, set the library path before anything else, since a missing DYLD_LIBRARY_PATH fails at startup rather than at build.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 1 day ago.
- What is it written in?
- Mainly C#, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- PintaProject/Pinta4,137 ★ · +83
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| PintaProject/Pinta | 4.1k | 4.1k |
83 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Two build systems, and only one of them installs
Every platform section of the README ends with the same two commands, a build and a run:
dotnet build
dotnet run --project PintaLinux has a second option, and the README labels them. Option one is for development and testing and is the pair above. Option two is for installation, and it is an autotools sequence: run `./autogen.sh`, or `./configure` if you are building from a tarball, add a `--prefix=<install directory>` argument to install somewhere other than `/usr/local`, then `make install`.
So the project is a .NET application that also knows how to install itself the way a Unix package does, and the tree carries the machinery for it: `Makefile.am`, `autogen.sh`, `configure.ac`, a pkg-config template in `pinta.pc.in`, an `xdg/` directory for desktop integration and a `po/` directory for translations. A pkg-config file is the giveaway, since nothing in a managed application needs one except a native-style install.
The division of labour is sensible but the README does not explain it, so a reader has to infer that the autotools path exists for distribution and the dotnet path exists for work.
Windows dependencies are MSYS2 clang packages
The Windows section starts before it mentions .NET, with a toolchain from a different ecosystem. Install MSYS2, then from the CLANG64 terminal run:
pacman -S mingw-w64-clang-x86_64-libadwaita mingw-w64-clang-x86_64-webp-pixbuf-loaderThe ARM64 case is handled by substitution rather than by a second command: use the CLANGARM64 terminal and replace `clang-x86_64` with `clang-aarch64`. So a Windows build needs two package names rewritten by hand on ARM hardware, and the WebP image loader is part of that required pair rather than an extra.
After the packages, there are two ways to build. Open `Pinta.sln` in Visual Studio with .NET 10 installed through the Visual Studio installer, or install the .NET 10 SDK and use the command line. The repository carries a solution file and two central `Directory.*.props` files, which is how the package and version references are shared across the seven projects in the tree, from Pinta.Core and Pinta.Docking through Pinta.Effects, Pinta.Gui.Addins, Pinta.Gui.Widgets, Pinta.Resources and Pinta.Tools.
macOS needs its library path set by hand
The macOS section is short and contains the one step that is easy to miss. Install .NET 10 and GTK4 with a single Homebrew line covering the runtime, the Adwaita library and icon theme, gettext and the WebP image loader. Then set a library path in the environment, and the value depends on the machine: `/opt/homebrew/lib` on Apple Silicon and `/usr/local/lib` on Intel, in both cases so that Pinta can load the GTK libraries.
That is two lines of environment configuration, and it is not a build-time concern. The build succeeds either way; what fails without it is the application finding GTK at startup, which is a worse way to discover the setting than a compiler error.
The rest of the section is the same build and run pair as everywhere else, so the cross-platform picture is that Pinta is a managed application whose three native dependencies, Adwaita, its icon theme and the WebP loader, are each installed by a different package manager on the three systems: pacman on Windows, Homebrew on macOS and apt on Linux.
GTK 4.18 and libadwaita 1.8, with one release's apt line
The Linux instructions give a floor and a package list, and both are specific:
sudo apt install autotools-dev autoconf-archive gettext intltool libadwaita-1-devThe minimum library versions are GTK 4.18 or newer and libadwaita 1.8 or newer, and the WebP image loader is listed as an optional dependency. Then there is the qualifier that tells you how much to trust the line above it: the instructions are written for Ubuntu 22.10 but should be similar for other distributions.
Two things follow. The floor is two library versions from 2025, which is a recent requirement for a project whose first release in the list is 3.1 from December 2025, and the single worked example is a 2022 distribution release, so anyone on a current LTS is extrapolating.
The WebP loader is also the clearest asymmetry in the documentation. It is required in the Windows pacman line and included in the macOS brew line, and it is optional on Linux. Whether that reflects the packages available or the state of each platform's build is not something the README says.
No Dockerfile, and the container instructions are someone else's repository
There is a section headed Building and Debugging in Docker, and its entire content is a sentence telling you to follow the instructions of a different project, a virtual development environment maintained in a named contributor's repository.
So the containerised workflow is not in this repository, while the Windows packaging is. The tree has an `installer/` directory for the Windows installer and no Dockerfile anywhere, and the only build definition files are `Makefile.am`, `autogen.sh` and `configure.ac` for the Unix path plus the two `Directory.*.props` files for the managed one.
That split is a reasonable division of labour, and it is also the kind of thing that quietly dates. A container recipe for a project with a .NET 10 target, GTK 4.18 and libadwaita 1.8 has to be updated when those floors move, and the person most likely to do that is whoever maintains the external environment rather than whoever maintains the editor. The README gives no version or date for that external project, so there is nothing in this repository that tells you whether it still matches.
MIT for the code, CC BY for two icon sets
The licensing section is the longest part of the README and it is not about the code alone. Original Pinta code is under the MIT License in `license-mit.txt`. Code from Paint.Net 3.36 is also used under the MIT License, and it retains the original headers on the source files, with Paint.Net's own licence text in `license-pdn.txt`. The project as a whole is MIT, and the copyright line in the README is Jonathan Pobst, 2010.
The icons are where it gets more interesting, because they come from four places under three terms. The Paint.Net 3.0 icons are under the MIT License. The Silk icon set is under Creative Commons Attribution 3.0. The Fugue icon set is also under Creative Commons Attribution 3.0. And icons contributed by Pinta contributors are under the same licence as the project itself, with the inventory of which contributor made which icon kept in a file inside the resources directory rather than in the top level.
So a distribution that ships the application binaries ships two CC BY 3.0 attributions and a per-icon provenance list that lives two directories down. That is a real compliance surface, and the README handles it in more detail than most projects handle their entire dependency licence.
The privacy statement is one sentence with an exception
The last section of the README is the code signing policy, and it holds three unrelated things. Windows binaries are signed for free through SignPath.io, with the certificate provided by the SignPath Foundation. Committers and approvers are the Pinta Maintainers, as a team page rather than a person.
And then the privacy policy, in one sentence: the program will not transfer any information to other networked systems unless specifically requested by the user or the person installing or operating it.
The shape of that claim matters. It is a default rather than an absolute, and the exception is not enumerated anywhere in the README. A user who wants to know what the exception covers has to read the code, and the sentence also does not say which network calls exist in the first place, so there is no baseline to compare against.
Everything else in the file points outward rather than inward: two distribution channels in the badge row, a Flathub application with a reverse-DNS identifier and a Snapcraft package, Weblate for translations, technical help and suggestions through GitHub Discussions, bugs through issues, an IRC channel on the GNOME network, a changelog for release notes and a separate patching guidelines document in the repository. The release line has been steady, with 3.1 on 2025-12-24, 3.1.1 on 2026-01-10 and 3.1.2 on 2026-04-02, and the last push to the default branch is dated 2026-10-03.
Editorial conclusion
Pick the install route that matches what you are doing, because the project offers two on Linux and they are not equivalent: dotnet run is for development, and only the autotools path honours a prefix and produces the desktop integration files. If you are on macOS, set the library path before anything else, since a missing DYLD_LIBRARY_PATH fails at startup rather than at build. And if you care about redistribution, read the icon licensing rather than the project's own, because two of the three icon sets are CC BY 3.0 with a per-file inventory that lives outside the top level of the repository.
Frequently asked questions
how to install pinta
Two distribution channels are linked from the README: a Flathub application with the identifier com.github.PintaProject.Pinta, and a Snapcraft package. Building from source needs .NET 10, GTK 4.18 or newer and libadwaita 1.8 or newer, and on Ubuntu the packages autotools-dev, autoconf-archive, gettext, intltool and libadwaita-1-dev. You can then run it with dotnet build and dotnet run --project Pinta, or install it with ./autogen.sh followed by make install.
What does Pinta need on Windows and macOS?
On Windows, install MSYS2 and run pacman -S mingw-w64-clang-x86_64-libadwaita mingw-w64-clang-x86_64-webp-pixbuf-loader from the CLANG64 terminal, using the CLANGARM64 terminal with clang-aarch64 in place of clang-x86_64 on ARM64. On macOS, install .NET 10 and GTK4 with brew install dotnet-sdk libadwaita adwaita-icon-theme gettext webp-pixbuf-loader, then set DYLD_LIBRARY_PATH to /opt/homebrew/lib on Apple Silicon or /usr/local/lib on Intel so the GTK libraries load.
Why does Pinta have two build options on Linux?
The README labels them by purpose. The first, dotnet build followed by dotnet run --project Pinta, is for development and testing. The second is for installation: run ./autogen.sh, or ./configure when building from a tarball, optionally with a --prefix argument to install somewhere other than /usr/local, then make install. Only the second path supports choosing an install directory, and the tree carries the autotools files, a pkg-config template, an xdg directory and a translations directory for it.
What licence is Pinta under?
The project is MIT, with the original code under license-mit.txt and code from Paint.Net 3.36 also under MIT, keeping its original source headers, with Paint.Net's licence text in license-pdn.txt. The icons come from four sources under three terms: Paint.Net 3.0 icons under MIT, the Silk and Fugue icon sets under Creative Commons Attribution 3.0, and contributor-made icons under the project licence, with the per-icon inventory kept inside the resources directory.
Does Pinta send anything over the network?
The README's privacy policy says the program will not transfer any information to other networked systems unless specifically requested by the user or the person installing or operating it. The exception is not enumerated in the file, and the README does not list the network calls the program makes, so the statement is a default rather than an inventory. The same section covers free Windows code signing through SignPath.io with a certificate from the SignPath Foundation.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/pintaproject-pinta)Star history chart for your README
[](https://hysenlabs.com/projects/pintaproject-pinta)Was this useful?