Paint.NET 5.2 Overhauls Layer Rendering, Adds Eight Effects and Experimental Wine Support

Release and availability​

The release was published on November 10, 2026. The Paint.NET blog's release post is dated 2026-11-10. Tweakers listed it a day later.

• Direct download: The classic desktop edition is free from the Paint.NET website.
• Microsoft Store: A paid Store edition is available. According to the developer, updates appear after Microsoft certification, usually within about a day.
• Other packages: Offline installers, portable ZIPs and deployment MSIs are on the official GitHub release page.
• Updating a desktop install: Go to Settings → Updates and click Check Now. Otherwise, wait for the automatic offer, which can take a few days.

Home users should pick the "anycpu" installer. The developer notes that anyone who doesn't know what an MSI is almost certainly doesn't want that download.

System requirements​

The official release page lists these requirements:

• Windows 11, Windows 10 v21H2, or Windows Server 2022.
• A 64-bit CPU with at least four cores. That means Intel/AMD x64 with AVX2, or ARM64.
• A GPU that supports Direct3D 11.
• An SSD.
• Optional: an HDR or wide-gamut display, and a Windows Ink pen or tablet.

The release page gives AVX2 examples: Intel Core 4th generation (Haswell, 2013) or newer, and AMD Ryzen 1st generation (2017) or newer. The CPU wording in the release notes is stricter than in the 5.1.12 notes. CPUs without AVX2 will still work but more slowly, and they are no longer part of the developer's testing and optimization. A CPU without SSE4.2 will not run the app at all. Fewer than four cores or an HDD should still work, but the developer calls them slower or unsupported.

If you run older hardware in a lab, a VM or a thin client, check for AVX2 and SSE4.2 before rolling this out. VMs that hide CPU features can cause trouble here.

A new file-type plugin system​

The old FileType plugin system dates back to Paint.NET 2.5 in 2005. It was tied to the internal Document, Layer and Surface classes. Those classes only supported the 32-bit BGRA32 pixel format and a flat list of bitmap layers.

The replacement works through interfaces such as IFileTypeDocument<TPixel> and ILayer<TPixel>. It sits on a typed imaging framework covering several pixel formats, pooled bitmap allocation, scaling and interpolation, quantization and dithering, format conversion and color management.

The point is to let the plugin API and the app's internals change separately. The developer says the system supports versioning, so published plugins keep working as new layer types, layer folders and blend modes arrive.

• Advice for plugin authors: Supply pixels in the file's native format, such as RGBA64, BGR24 or HDR RGBA FP16. Don't convert to BGRA32, because Paint.NET will handle conversion and color profiles. Plugins can query at runtime which formats are supported or native.
• Paint.NET.Plugin.SDK: A new NuGet package, Paint.NET.Plugin.SDK, is part of this release. Developers can reference it instead of manually pointing at assemblies in a local install. The classic and legacy plugin systems are not part of it.
• Deprecation status: The classic effects plugin system is fully deprecated, though existing plugins are said to keep working. The classic file-type system is at the first deprecation stage. It still compiles with a warning, and the developer plans to make that an error in the next major update.

Most users will never touch this. Everyone who relies on third-party format plugins, such as WebP, PSD or other add-on types, should watch for authors updating them. The old ones are not being cut off yet.

Rewritten layer renderer with FP32 precision​

The old renderer dated back to Paint.NET 1.0 in 2004. It used 8-bit unsigned integer precision per channel and had no SIMD optimizations. The developer says rounding errors accumulated across many layers and could cause wrong colors or banding.

The new engine uses 32-bit floating point per channel. It is optimized for AVX2, AVX512 and ARM64 NEON through .NET's platform-agnostic intrinsics. The developer says there is no perceptible slowdown despite the extra memory bandwidth, and that AVX512 CPUs such as AMD Zen 5 benefit most. Those are the developer's own claims, not independent benchmarks.

FP32 also serves as the canonical internal format. Every rendering kernel only needs to be written once, with conversion at the start and end of the pipeline. That makes high-bit-depth and HDR support in the rest of the app easier to add later. The renderer can handle it, but the rest of the app does not yet.

Other developer-reported improvements:

• Clipboard copy up to 95% faster.
• Temporary memory use cut by 50% for Edit → Paste into New Image.
• Improved zooming and scrolling on large images.
• A single rendering pass for zoom above 100%, which should save laptop power.
• Median Blur 10–50% faster, depending on quality.
• Histogram calculation for Levels and Auto-Levels about 20% faster.

HDR images: tone mapped on load​

Paint.NET 5.2 reads HDR metadata and tone-maps HDR to SDR when it opens supported files. The release notes name AVIF, HEIC, JPEG XL, JPEG XR and PNG. Earlier versions could open these files but clamped anything above 1.0, which often blew out the colors. The July alpha already described good-quality HDR-to-SDR tone mapping on open, including for plugin file types.

This is not native HDR editing. The developer says that is planned for the future, and the automatic tone-mapping step will be removed when it arrives. The release also adds CICP metadata support for AVIF, JPEG XL and PNG. HDR or wide-gamut displays can use their full gamut. SDR displays work in sRGB and clamp images to it.

Move Pixels and eight new effects​

The Move Pixels tool gains Nearest Neighbor (Antialiased) resampling, also called "sharp bilinear." It upscales with nearest neighbor to the next whole scale factor, for example 700% when you asked for 632%. It then downsamples with bilinear to the target. The result keeps a pixel-art look with smoother edges. It works for both scaling and rotation.

The eight new effects are:

The August alpha post says each new effect is also available to plugins in their Direct2D effect graphs.

Wine builds for Linux and macOS​

Experimental Wine support lets Paint.NET run on Linux and Mac. It is a separate package from its own GitHub repository, not part of the standard installer. The developer calls it "pre-alpha" and says it is for early adopters. He does not promise when, or whether, it will reach a stable and performant state.

The Wine repository lists these limits:

• Performance is below the native Windows build.
• Some file formats may fail to load, or lose color profiles and metadata, because Wine's codecs are incomplete.
• Cosmetic UI problems remain, including an incorrect toolbar.
• Printing and scanning do not work.
• The portable build has no automatic updates. Builds expire 12 weeks after they are built, so users need to fetch a newer one.
• The repository states a minimum Wine version, 11.21 at the time of its writing.

This is a compatibility experiment, not a native port. Treat it that way.

What is coming in 6.0​

The developer says the next big update will bring a new .PDN file format. High-bit-depth pixels, new blend modes and layer folders are planned first. Adjustment layers, text layers and HDR are possible later additions. These are roadmap statements, not 5.2 features and not promised dates.

Practical takeaways​

• Most Windows users: If your hardware meets the AVX2 and four-core guidance, 5.2 should be a straightforward upgrade. Check plugins first if you rely on third-party file types.
• Older or virtualized hardware: Confirm SSE4.2 support. AVX2 is no longer something the developer tests for.
• HDR image users: Expect tone-mapped SDR output, not an HDR editing workflow.
• Plugin authors: Start moving to the new FileType system and the NuGet SDK before the classic system's warnings turn into errors.
• Linux and Mac users: Try the Wine build if you like experiments, and don't treat it as production software.

For a free image editor, 5.2 is a substantial technical overhaul. The long-term payoff depends on 6.0 and the .PDN format actually shipping.