Add-ons: Site

The Pale Moon Add-ons Site is a service provided by the Pale Moon project. The intent of the service is to facilitate indexing and hosting of extensions, themes, and search plugins for use in the Pale Moon browser. However, the backend software known as Phoebus serves more than just Pale Moon.


The Add-ons Team

The Add-ons Team performs the day-to-day administration and coordination of all the Add-ons Sites.


  • FranklinDM
  • Moonbat


  • Lootyhoof aka Ryan659
  • Andrew Gilbertson aka AndyTheAbsurd
  • Antonius32

Site Administrators

Phoebus Administrators have unrestricted access to the Phoebus software, all Add-on Sites, and the hosting server itself. You likely shouldn't need to contact them.

  • Moonchild

Submitting your add-on

So, you decided to bring your add-on to Pale Moon officially, have forked your own version for us, or have simply been awesome and created something new? That is fantastic! You have (or will) let the community chew it up a bit and think it is ready for a proper release... So what do you do?

Well, you have a couple options, but each one must be considered carefully.

Hosting your add-on

The service will provide full hosting of your add-on, a dedicated page, and automatic update services.

As of Phoebus 2.0, the software now has a dedicated control and management panel located on most Add-on Sites including the one for Pale Moon.

You might also be interested in the phoebusCode syntax.

Indexing your add-on

This is known informally as an External. Indexing is available to both extensions and themes will list your extension to the category of your choosing and will link to where users can obtain your extension.

This solution is a great choice for maintaining your independence and choice of infrastructure and distribution. You may, for example, want to host your extension on your own website or source code repository's downloads section.

For the Add-ons Manager's Automatic Update Service you must include in your install.rdf file an "em:updateURL" tag to a well formed XML (RDF) file on your own service. You must also take into account that you must not set any cache headers on XPI files if you use HTTPS because cached items do not contain the original security information and will cause issues and therefore will be rejected by the XPInstall routine as insecure.

You should submit a request to the Add-ons Team (via the forum's Private Message system) with the following information:

  • Add-on's name
  • A 64x64 alpha-transparent icon in the PNG format (we can use the generic green puzzle piece if you simply don't have one)
  • For themes, a toolbar screenshot like those for hosted themes
  • The "em:description" text as you define it in your install manifest for the category listing (~240 character limit)
  • Category to be listed in (only one per add-on is allowed at this time; additionally, themes do not use categories at this time and some Add-ons Sites do not currently list by category, but it is important to have one set): see the full list here.
  • URL where you host your add-on

In this case we will not be able to display a full content page or any other metadata for your add-on. It is up to you to provide these on the page you want us to link to in the category listing.

Review Process

Before your add-on is published, it undergoes a review process in which the Add-ons Team examines its contents and associated metadata.

These are the things that what we commonly look out for in your submission (not an exhaustive list):

  • Name similarity to existing and/or established add-ons
  • Chosen add-on slug*
  • Source code
  • Presence of disallowed properties in the install manifest (e.g., updateURL)**
  • Invalid maximum target application version (using a wildcard or an extremely high maximum version number)
  • Impact to application stability and functionality
  • Compliance with the license if it was forked***

*Every extension on the Pale Moon add-ons site has an internal identifier (a "slug") which is a short and unique ID for each add-on. Slug squatting is not allowed, where an extension developer would choose a slug for their extension that is a common name or ID for an existing add-on not belonging to them, e.g., if someone would make an adblocker extension and give it the slug "adblockplus" while it isn't Adblock Plus. It's considered an etiquette issue and a grey area to avoid.

**Update-related properties are allowed for external/indexed add-ons.

***See this forum post for more information.

With this, we can decide if it is approved for release to the add-ons site, still needs further changes, or rejected. Expect that you will be contacted either via the forum or with the e-mail address that you used to register in the panel.

However, your submitted add-on might not be reviewed immediately for a variety of reasons. You may bring this to the Add-ons Team's attention by requesting a review manually (via the forum's Private Message system) with the following as your subject:


Site design and Branding © 2024 Moonchild Productions - All rights reserved
Any other content, brand names or logos are copyright or trademark to their respective owners.
Policies: Cookies - User Content - Privacy.

The Pale Moon Developer Site is powered by Project Selene 1.2.1.