paint.net

documentation

Revision Date: 27 February 2024

Installing Additional Plugins paint.net plugins icon

Paint.net allows for easy expansion of features and file types through a plugin system.  Many plugins are available. Examples of plugins include support for new type of file formats, drop shadows, coloring tools and photographic adjustments.  There is even a plugin called CodeLab which is a plugin designed to create new plugins!

Plugins are developed by third-party developers and released via the paint.net forum | plugins.

A comprehensive list is of plugins is compiled and maintained here paint.net forum | plugin index.

Please note that plugins are provided by members of the forum. The paint.net team cannot provide support for them.  If you require assistance with an individual plugin, visit the paint.net forum and post a question in the thread where the plugin was released.


There are two types of plugins:

Note

Plugins are developed and maintained by the paint.net community and not the developer of paint.net.  If you are having issues with a particular plugin, please ask on the paint.net forum in the thread where the plugin was downloaded.  This location can be found by searching from within paint.net. Open the search URL with the keyboard combination Ctrl + E.

Warning

Only ever download plugins from the paint.net forum, or from links posted there by the plugin author.  Never download plugins from any other source as malware, viruses and infected files can infiltrate your system.
We highly recommend you perform a virus scan on any plugin prior to installation.

Plugins come as a file with the extension of ".DLL".  Some plugin authors may compress these files further in an archive format such as .ZIP or .RAR. If compressed, the plugin will need to be extracted from the archive file to it's *.DLL format before proceeding.

.DLL Icon
.DLL Icon

Classic paint.net

For Classic paint.net, locate the directory where paint.net has been installed. Usually this is "C:\Program Files\paint.net\".  It is also possible to use the directory "Documents\paint.net App Files\..." as an alternative, but it will usually need to be created manually (see Microsoft Store version below).

PDN Directory
Default Classic paint.net Directory

Microsoft Store paint.net

In the Windows Store version of paint.net, the directories for plugins and Shapes are different. These locations need to be created manually.

First navigate to your Documents folder (this may be translated to your system language). In it, create a new folder called paint.net App Files
Then create three subfolders in the new folder. These should be called: Effects, FileTypes and Shapes.
The correct spelling of these folder names is essential, however Windows and paint.net will ignore the capitalization (or lack of).

Plugin Folders - PDN Store version
Manual creation of plugin folders (store version of paint.net)

Paint.net Portable

Plugins for paint.net portable go in the same folder as the installation, so locate the same directory where paint.net was unzipped. In that directory there will be folders for Effects, FileTypes, and Shapes.

For all installations....

If you downloaded a FileType plugin, move the uncompressed *.DLL to the \FileTypes\ subdirectory.

If you downloaded an Effect plugin, move the uncompressed *.DLL file to the \Effects\ subdirectory.

If the new plugin is replacing an older version you may be prompted to confirm the replacement of the existing file. It is safe to do so.

Navigate to the plugin file just moved and Right-click on the file. Select Properties from the context sensitive menu.

.DLL Properties
Plugin Properties

Under the "General" tab, look for an Unblock button next to the Security label.  If the button is present, click it to unblock the file and allow it's use on the computer. Skip this step if there is no Unblock button in the Properties dialog.

Close paint.net if it was open.

Reopen paint.net to enjoy the new features the plugin has added.

Note

paint.net scans for plugins only at start-up. The application must be restarted to load new plugins.

For Effect plugins; the plugin developer should have posted the location of the plugin so it can be found in paint.net's menu system.  If the plugin cannot be found in the correct menu, check the Settings dialog under the Plugin Errors tab to see if there was a problem loading it.

For Filetype plugins; the plugin will not be found in paint.net's menus. Instead, the plugin will add the new file extension to the drop-down lists in the load and save dialogs.  If the new extension cannot be found, check the Settings dialog under the Plugin Errors tab to see if there was a problem loading it.

Custom Plugin/Shapes Folders paint.net plugin folder

You can specify additional directories where plugins will be loaded from. This means cloud-based solutions like OneDrive can be used to host plugins which will then be sync'd to all of your systems. For security reasons enabling this feature requires editing registry entries.

Warning

Setting up custom plugin folders, especially cloud-based folders, is advanced app configuration. This configuration is intended for advanced users, administrators, and IT Professionals as it requires administrator privilege and the creation of registry keys. For your protection, we recommend backing up the registry before modifying it.

The creation of custom plugin folders involves the creation of two registry keys:

  1. Set HKEY_LOCAL_MACHINE \ Software \ paint.net \ "Plugins/AllowAdditionalPluginDirectoryRoots" (without the quotes) to true.
  2. Set HKEY_CURRENT_USER \ Software \ paint.net \ "Plugins/AdditionalPluginDirectoryRoots" to a semicolon-delimited list of directories (just like setting PATH).

Within the custom directories, create the usual subdirectories of FileTypes, Effects, and Shapes. You can use environment variables like %OneDrive%\Documents\paint.net Plugins.

The portable version of paint.net cannot use this feature.

Paint.NET Plugin API Documentation

For plugin developers, the Paint.NET plugin API documentation and reference material can be found on github: Plugin API Docs