How can I open a PDN file without Paint.NET?
Open the `.pdn` file in PhotoCraft using File › Open or drag and drop. Review the warnings and save as `.pcraft`, PSD, or PNG.
Paint.NET file guide
Yes. PhotoCraft opens Paint.NET PDN3 `.pdn` files without Paint.NET, .NET, Python, or an external converter. Each bitmap layer remains editable, including layer order, Unicode names, visibility, opacity, pixel alpha, and all 14 PDN3 blend modes. PDN support is import-only: PhotoCraft cannot save back to `.pdn`, does not retain all Paint.NET document metadata, and cannot reproduce every future Paint.NET effect. Save as `.pcraft` for the most complete editable continuation, or export PSD/PNG after reviewing the compatibility warnings.

Paint.NET is the complete native choice for PDN read, write, and its effect ecosystem. PhotoCraft is the free route for opening supported PDN3 layers without Paint.NET. Photoshop and Photopea require an export or conversion before they can work with Paint.NET documents.
| Editor | License | Platforms | Pricing | PDN workflow | Best for |
|---|---|---|---|---|---|
| PhotoCraft | MIT OR Apache-2.0 | macOS, Windows, Linux, FreeBSD, Web | Free | Reads PDN3 bitmap layers and all 14 blend modes; PDN export is unavailable | Opening Paint.NET documents without Paint.NET and continuing supported work in .pcraft |
| Paint.NET | Proprietary | Windows | Free download with optional donation | Native PDN read/write, Paint.NET effects, and the complete Paint.NET document model | Complete native PDN editing, Paint.NET effects, and saving changes back to PDN |
| Adobe Photoshop | Proprietary | Windows, macOS, iPad, Web | Subscription | No native PDN editing; Paint.NET must export another format first | Adobe-centric work after the PDN document has been converted to PSD or a raster format |
| Photopea | Proprietary web app | Browser | Free core editor with optional paid upgrades | Browser PSD and raster workflow; PDN requires an export or conversion step | Quick browser access after the Paint.NET document has been converted |
Comparison reviewed 2026-11-12. Pricing and licensing can change; verify each vendor’s current terms before purchase.
Yes. PhotoCraft recognizes PDN3 documents, reads their bitmap layers and blend modes, and opens them as editable PhotoCraft layers without requiring Paint.NET.
The importer understands Paint.NET’s typed object structure, both newer and older blend-operation records, BGRA32 pixel surfaces, gzip or raw numbered chunks, shared pixel memory, and padded rows. It validates references, dimensions, strides, counts, checksums, and decode limits before exposing the document.
This is a native import rather than a screenshot or flattened thumbnail. The resulting quality still depends on the exact PDN version and features used, so keep the original source until the converted document has been checked.
Install an official PhotoCraft build, use File › Open or drag the `.pdn` file onto the app, review the import warning, and save a new supported document.
Start from a copy and inspect the layer order, names, visibility, opacity, alpha, and blend modes. Paint.NET effects and metadata that PhotoCraft cannot represent are surfaced during import rather than silently discarded.
Save as `.pcraft` when the goal is to keep every supported layer and blend mode. Export PSD only after checking the warnings because six Paint.NET-specific blend variants do not have exact Photoshop equivalents.
Bitmap layers remain editable with layer order, names, visibility, opacity, and pixel alpha. All 14 PDN3 blend modes are supported, including the Paint.NET-specific Reflect, Glow, Negation, XOR, and two Color dodge/burn variants.
Painting, masks, transforms, reordering, duplication, and undo use the same commands as other pixel layers. That makes the imported document useful for continued editing rather than only inspection.
The six modes without exact Photoshop equivalents remain identifiable in PhotoCraft. Exporting them to PSD can change blending to Normal, so `.pcraft` is the safer editable continuation when those modes are essential.
PhotoCraft does not preserve all Paint.NET document metadata, and unsupported PDN layouts or future effects can fail or be reported rather than reconstructed.
Paint.NET print resolution, color profiles, and nonempty user metadata are currently omitted or flagged. A layer’s visible pixels can survive while document-level workflow information does not.
The importer validates malformed and truncated files instead of attempting unsafe recovery. For damaged files or unsupported future versions, open the source in Paint.NET and export a standard PSD or layered interchange format.
No. PDN support is import-only. Save as `.pcraft` for PhotoCraft’s editable format, or export PSD/PNG after validating the destination limitations.
A `.pcraft` document preserves the layers and PDN-specific blend modes that PhotoCraft successfully imported. Exporting to a flattened PNG produces the expected single image without layer editability.
A PSD export is useful when another Adobe-style editor needs a layered document, but six Paint.NET variants may be changed to Normal with a warning. Treat the destination format’s limits as part of the conversion.
In the current PDN3 test corpus, small Paint.NET 4.0.10 documents matched their embedded previews within 2.142/255. A separate 5.x file also passed layer editing and save tests.
Older Paint.NET versions rounded between layers while PhotoCraft keeps floating-point precision, so layered composites are not necessarily byte-identical. The corpus is useful evidence, not a guarantee for every Paint.NET release or effect.
Compare the largest representative file at full resolution. Inspect hidden layers, partial alpha, unusual blend modes, text or effects rasterized by Paint.NET, and any metadata your downstream workflow requires.
Use Paint.NET when you need native PDN saves, Paint.NET effects, its exact layer behavior, or a Windows-only Paint.NET workflow.
PhotoCraft is the stronger choice when Paint.NET is unavailable, when the work must continue on macOS or Linux, or when a Photoshop-style layered document is the destination. The product differences are real: PhotoCraft does not claim Paint.NET effect or document-level parity.
The best workflow is often to use Paint.NET for the original editing session and PhotoCraft for inspection and conversion when the document must leave Windows.
PhotoCraft is a practical free way to open supported PDN3 layers outside Paint.NET and continue editing in another format. Paint.NET remains required for native PDN saves and complete Paint.NET-specific behavior.
Open the `.pdn` file in PhotoCraft using File › Open or drag and drop. Review the warnings and save as `.pcraft`, PSD, or PNG.
Supported bitmap layers retain order, names, visibility, opacity, pixel alpha, and all 14 PDN3 blend modes. Unsupported metadata is reported or omitted.
No. PDN support is import-only. Use Paint.NET for native PDN saves or continue in PhotoCraft with `.pcraft`.
Photoshop does not natively edit PDN files. Export a layered PSD or another supported image format from Paint.NET first.
Reflect, Glow, Negation, XOR, and Paint.NET’s separate Color Burn and Color Dodge variants have no exact Photoshop equivalent and can be changed to Normal with a warning.
The Web build accepts `.pdn` files, subject to browser memory limits and the same PDN3 importer limitations as the desktop build.
Download the desktop build, keep your source documents, and compare the layers and output against your current workflow.
We use primary vendor and project sources for product features, licensing, and platform claims. PhotoCraft-specific technical details come from its public repository and release documentation.