The first preview build of Paint.NET 5.0 is now available!
There’s a huge write-up with a ton of information, screenshots, and download links over on the forum. It was too much to convert into a blog post, so just head over there
The first preview build of Paint.NET 5.0 is now available!
There’s a huge write-up with a ton of information, screenshots, and download links over on the forum. It was too much to convert into a blog post, so just head over there
This update includes a new Layers -> Toggle Layer Visibility (keyboard shortcut: Ctrl + comma) command, some performance improvements, bug fixes, and a new IndirectUI control for plugins (FolderChooser).
NOTE for Windows 7, Windows 8.1, and 32-bit/x86 users: Paint.NET v4.3.x will be the last release(s) that work on Windows 7, Windows 8.1, or on any 32-bit/x86 version of Windows. It has become significantly more difficult and time consuming to support these lately, not very many people are using them, and I can no longer justify the cost and frustration of keeping support for these afloat. Starting with Paint.NET v4.4, only Windows 10 and 11+ will be supported, and only on 64-bit (x64 and ARM64). Updates for 4.3.x will be released on an as-needed basis and only until v4.4 is completed.
Get the update
To get this update, make sure you have "Also check for pre-release (beta) versions" enabled in Settings, and then click on the Check Now button. (Unfortunately alpha/beta releases are not currently available for the Microsoft Store version of the app).
You can also download the online/web installer at the forum.
Offline installers, portable ZIPs, and MSIs for deployment can be found over at the GitHub releases page.
Changes since 4.3.7:
Enjoy!
This is a hotfix for a crash in the box filter rendering kernel, which is used to generate mip-maps for the canvas when zoomed out.
NOTE for Windows 7, Windows 8.1, and 32-bit/x86 users: Paint.NET v4.3.x will be the last release(s) that work on Windows 7, Windows 8.1, or on any 32-bit/x86 version of Windows. It has become significantly more difficult and time consuming to support these lately, not very many people are using them, and I can no longer justify the cost and frustration of keeping support for these afloat. Starting with Paint.NET v4.4, only Windows 10 and 11+ will be supported, and only on 64-bit (x64 and ARM64). I have started working on v4.4 and will only release v4.3.x updates on an as-needed basis and only until v4.4 is completed.
Get the update
Changes since v4.3.5:
Since this is a hotfix, here’s what was in v4.3.5 compared to v4.3.4:
Enjoy!
This is a hotfix for 4.3 alpha build 4894, which was published yesterday.
Get the update
To get this update, make sure you have "Also check for pre-release (beta) versions" enabled in Settings, and then click on the Check Now button. (Unfortunately alpha/beta releases are not currently available for the Microsoft Store version of the app).
For direct download links, please visit the forum.
Changes since 4.3 alpha build 4894:
There’s quite a lot to like in this build. Primarily, I’ve spent some time optimizing the snot out of the Magic Wand and Paint Bucket tools. They are now immensely faster, which you’ll especially be able to notice when working with larger image. I’ve written about this in more detail over on Twitter: https://twitter.com/rickbrewPDN/status/1424902298367451137
For this update I’m also switching over to something called self-contained deployment. This means that installing .NET is no longer required, as all the necessary files are bundled with the app. You should not see any change in functionality, this is a "transparent" change. The download size and disk space requirements are much larger, but it simplifies a whole of things that have been problematic over the years. I’m not 100% sure I’m going to stick with this, but it’s something I’d like to keep as long as I don’t get some warning from my hosting provider about my bandwidth usage. Startup performance should be slightly (5%) improved as a result of tighter ahead-of-time compilation.
You’ll note, however, that the download link for the installer is quite small — only about 1.7MB — because I’m testing a new "web" installer. What you’re downloading here is a stub installer that will download the rest of the app and then install it. The reason for doing this now is that I need to make sure it gets some test coverage before I utilize it later for folks who will be updating from pre-4.3 to 4.3+. The web installer is also really important to make sure folks who’ve installed pre-4.3 on ARM64 will get the correct native build. Before, the x86/x64 version would be used on ARM64 and would run emulated, but now this will permit those devices to smoothly transition to the native ARM64 build.
Get the update
To get this update, make sure you have "Also check for pre-release (beta) versions" enabled in Settings, and then click on the Check Now button. (Unfortunately alpha/beta releases are not currently available for the Microsoft Store version of the app).
For direct download links, please visit the forum.
Changes since 4.3 alpha build 7881:
Here are the other changes that 4.3 has when compared to 4.2.16:
Paint.NET has finally been migrated to .NET 5! If you’re not familiar, .NET 5 (also known as .NET “Core” 5.0) is the new version of .NET that replaces .NET “Framework” (of which no more new versions will be made). More info here: https://devblogs.microsoft.com/dotnet/introducing-net-5/
It was a very large effort to move Paint.NET over to .NET 5 over the last 2 months! Most of that effort went towards rebuilding from scratch how Paint.NET is built and packaged (installer, MSI, APPX, portable ZIPs), because the old solutions were showing their age and were no longer serviceable. The app itself required only minor changes to work on .NET 5.
You should not really see any difference in the app’s features or the way it behaves, although performance has improved. Sometimes substantially! Sadly there are some plugins that will no longer work, although I may be able to find fixes for some of them.
I will be releasing this via the built-in updater sometime later this week. For now, I want to start with a smaller audience, so you must download and install it manually. Just close the app, run the installer EXE inside the ZIP, and it will do everything for you (as usual):
The download link for the installer is available at the forum page about this release.
You may also download a portable version of the app, which is useful if you just want to try things out or are not yet ready to fully commit to the new version. .NET 5 is built-in, so there is no need to install it (the app is “self-contained”). The portable version of the app will save settings in a local JSON file instead of using the registry.
The downloads links for the portable ZIPs are available at the forum page about this release.
If you have an ARM64 device such as the Surface Pro X, you may also install the app. For the portable ZIPs, use the architecture appropriate for your operating system: x86 for Win10, or x64 for Win11. This is untested, so please report back with how well it works.
Changes:
Known Issues:
Hot on the heels of 4.2.16 beta build 7765, this build fixes a new issue when saving images at 8-bit color depth if they have transparency (as reported here and in a few other posts: https://forums.getpaint.net/topic/118074-autodetect-bit-depth-on-saving-png-files-fails-on-beta-4216776543041/)
To get this update, make sure you have "Also check for pre-release (beta) versions" enabled in Settings, and then click on the Check Now button. (Unfortunately alpha/beta releases are not currently available for the Microsoft Store version of the app).
You can also download it directly on the forum.
Change log:
Now that I’m getting back into the swing of things after having moved across the country (Bay Area -> back to Seattle area, finally!), it’s time for a new update
This release is mostly focused on fixing, improving, and optimizing the quantization code. This is used when you save an image at 8-bit or lower color depth. There have been a number of bugs that have plagued this over the years, including 1) the generated palette is way too small (e.g. for a black->red gradient, it’d be 64 colors instead of 256), 2) the generated palette is slightly too small (e.g. 252 colors instead of 256), 3) the precision of the colors would be biased in favor of those that are at the top of the image, 4) the palette has colors removed from it that shouldn’t have been (this plagues Auto-detect), and more recently 5) the generated palette, especially for a low color depth, is complete trash.
#1 was a result of a bug in the Octree code that goes all the way back to the MSDN article it was pulled from, https://docs.microsoft.com/en-us/previous-versions/dotnet/articles/aa479306(v=msdn.10)?redirectedfrom=MSDN . As it turns out, shifting right (via >>) by a negative amount results in 0 instead of a shift left. Maybe C works that way, but C# does not.
#2 was a result of the way that reduction/merging works in the Octree data structure. It can only merge an entire node’s children, meaning it can reduce 8 colors into 1, but never 8 colors into 2 through 7. This means it would undershoot the desired palette size as much as 6/7th of the time. I fixed that with a trick I learned at https://www.codeproject.com/Articles/109133/Octree-Color-Palette (search for the word "vomit" ).
#3 happens because the Octree code would reduce nodes in an order defined by how they were added to the octree. Since the image is processed top-to-bottom, this would thus favor colors that first appear at the top. I’ve fixed this by more evenly spreading out which leaf nodes are merged — those with lower frequencies are merged first, and if two colors have the same frequency then the ordering is deterministically pseudo-randomized by using the color’s hash code.
#4 was kind of a mix between 1, 2, and 5. There have been several reports of images that should be correctly auto-saving at 4-bit color depth (because of using <=16 colors), but colors are still trimmed. Auto-detect is strictly required to be lossless, and it has been failing at that. My new code for the Octree algorithm should fix this, but I’ve also added code to skip palette generation entirely if the desired color count is greater than the # of unique colors in the image (an obvious shortcut/fix, but the code was a bit snaky in terms of permitting this). This also means Median Cut will behave properly, because WIC’s code does not necessarily do this correctly either.
#5 was a result of switching from my Octree code to WIC’s Median Cut. As it turns out, Median Cut isn’t a good choice for a lot of images even when it’s correctly implemented. In addition to having some really bad bugs with large images that I’ve had to work around, WIC’s implementation also falls completely flat on its face when the palette size is small. Imagine a black->white gradient that gets bits of cyan and magenta sprinkled throughout. Ugh. I have retained the ability to use Median Cut, although Octree is the default.
I’ve also optimized these things to be a lot faster and use a lot less memory.
You can see all of this in effect if you save an image as a PNG, GIF, TIFF, or BMP at 8-bit, 4-bit, 2-bit, or 1-bit color depth. You can also use the new Effect -> Color -> Quantize effect to play around with it. It lets you specify an exact palette size instead of the bit-depth.
To get this update, make sure you have "Also check for pre-release (beta) versions" enabled in Settings, and then click on the Check Now button. (Unfortunately alpha/beta releases are not currently available for the Microsoft Store version of the app).
You can also download and install this build directly on the forum.
Change log:
This release is going pretty smoothly! I just had to fix a few small things that were pointed out in the forum thread for the alpha release, and get the translations up-to-date.
To get this update, make sure you have "Also check for pre-release (beta) versions" enabled in Settings, and then click on the Check Now button. (Unfortunately alpha/beta releases are not currently available for the Microsoft Store version of the app).
You can also download and install this build directly on the forum.
Changes since 4.2.15 alpha build 7683:
This is a small update that improves some quality-of-life issues, and fixes some important crashes due to mishandling of some non-fatal DirectX errors.
To get this update, make sure you have "Also check for pre-release (beta) versions" enabled in Settings, and then click on the Check Now button. (Unfortunately alpha/beta releases are not currently available for the Microsoft Store version of the app).
You can also download and install this build directly on the forum.
Changes since 4.2.14:
Enjoy!