Pterodactyl v2: What's Changing and How Hosts Should Prepare

Pterodactyl 2.0 has a tagged open beta and an official upgrade guide. Here is what changed, which versions are supported, and how to rehearse a safe move from 1.x.

Pterodactyl v2 game server panel with its new extension system

Pterodactyl 2.0 is in open beta. The latest tagged beta checked on 24 October 2026 is v2.0.0-beta.2. The latest stable 1.x release is v1.15.2. The project recommends keeping customer panels on 1.x while testing v2 on a copy.

The beta brings an Extension SDK, a unified React 19 admin and client app, Laravel 13, an egg catalog and theme support. It remains free under the MIT license. Check the official release notes before any upgrade: beta requirements and extension compatibility can change.

Where Pterodactyl v2 stands right now

The beta.1 release introduced the main v2 features and lists Extension SDK 2.0.0-beta.6. Beta.2 fixes an egg-export issue. These are tagged releases; older references to an untagged alpha, SDK beta.4 or a fixed six-month 1.x support window are outdated or unverified. The release notes do not announce a stable v2 date or a guaranteed 1.x support deadline.

For a new beta install, the release notes list PHP 8.3 or 8.4, MariaDB 10.11 or 11 or MySQL 8 or 9, Redis, and Ubuntu 22.04/24.04 or Debian 12/13. Follow the current installation guide for complete requirements.

What's new in Pterodactyl v2

An Extension SDK instead of core edits

This is the change that matters most for anyone selling or running addons. According to the README, v2 lets you extend the panel through a versioned API instead of editing core files, so changes survive updates. The SDK README goes further:

  • Extensions register components into named slots (the example uses server.console.before) and add their own screens to the server, account or admin areas, declared in an extension.json manifest.
  • Extensions can register their own subuser permissions, named ext.<id>.<key>, which show up in the server's user editor.
  • Everything exported from @pterodactyl/sdk is semver-governed: additions are minor versions, removals are majors. That is the promise that should stop updates from breaking addons.
  • Each slot has its own error boundary, so a crashing extension should not take the whole page down. The README is honest that this is not a sandbox: native extensions still run in the panel's JavaScript environment.
  • Enabling, disabling or updating an extension takes effect on the next full page load.

On the backend, the changelog lists action contracts that extensions can call and wrap (file reads, directory listings, server logs, live server state, egg changes and login completion), plus hooks to register commands, schedules, head tags and root routes. Extension settings get colour, textarea, multiselect, list and file fields, with uploads served from /extension-files/<id>/.

There is also a conflict rule worth knowing about. Each extension that uses Tailwind must declare its own prefix of 2 to 12 lowercase letters, two enabled extensions cannot share one, and the panel rejects builds whose utilities do not carry the declared prefix. In plain terms: one extension's CSS should no longer break another's layout, which anyone who has stacked several v1 addons will appreciate.

Official extensions and how you install them

The Pterodactyl team publishes example extensions in pterodactyl/extensions. Right now there are four:

  • Announcements: panel-wide banners users can dismiss.
  • Custom Buttons: admin-defined link buttons and sidebar items on the server page.
  • Dark Theme: a deeper neutral dark theme that also works as a template for your own.
  • Redirect: short links served by the panel, such as /go/discord.

Installing one is a single command on the panel host, after downloading its zip from the latest release:

php artisan p:extension:install /path/to/dark-theme.zip --enable

Then reload the panel. Extensions can be disabled or removed again from Admin > Extensions. Note that the same README says the SDK is not published to npm yet, so developers currently build against a local clone of the 2.0-develop branch.

Those example manifests reflect the versions at which they were built. The beta.1 release notes name SDK 2.0.0-beta.6; check each extension's current manifest against your installed panel and SDK release before enabling it.

A modernised stack and a single React app

The README lists Vite, React 19, TanStack Router and Query, Tailwind 4 and Laravel 13, and says the admin and client areas are now a single React application with one design. If you have spent years with the old separate admin area, this is the biggest visible change.

Egg importer and design-token theming

Two smaller features with real day-to-day value: a one-click egg importer that lets you browse the egg catalog and import directly from the panel, and theming with design tokens so you can restyle the panel without rebuilding it. The changelog shows how far the token system already goes, with tokens for layout, terminal, selection, scrollbars and browser chrome, plus an optional sidebar sub-navigation mode.

Pterodactyl v1 vs v2 at a glance

1.x2.0 open beta
Release statusStable; latest tag v1.15.2 at reviewv2.0.0-beta.2 at review; test on a copy
RuntimeCheck the installed 1.x release requirementsPHP 8.3/8.4, Redis and supported MySQL/MariaDB versions
FrontendExisting admin and client interfacesUnified React 19 app; Laravel 13 backend
ExtensionsExisting v1 addon ecosystem, often with core changesVersioned Extension SDK; validate each beta-compatible package
UpgradeKeep production current on 1.xOfficial 1.x upgrade guide; rehearse on a copy

Upgrade path and remaining unknowns

The project now publishes an official 1.x-to-v2 upgrade guide. Bring 1.x to at least 1.12 (preferably the latest 1.x), check PHP 8.3 and the intl extension, and update billing integrations that use removed nest endpoints. Back up the database, .env and panel files. The guide installs v2 in a separate directory, migrates the copied database and then swaps directories. It explicitly says not to use the old p:upgrade path for this major upgrade. Rehearse with a copy first.

For an earlier v2 beta, use the separate beta update guide. A stable release date, fixed 1.x support deadline and compatibility of individual third-party themes or addons remain unconfirmed; check each developer's release notes.

How to prepare your hosting business for v2

  1. Keep production on current 1.x while v2 is beta. Plan a test window and read the latest release notes rather than relying on an assumed support cutoff.
  2. Check the host. Confirm PHP 8.3/8.4, intl, Redis, supported database and operating-system versions; check your Wings and billing integration requirements too.
  3. Inventory custom work. List each v1 theme, addon, Blueprint extension and core patch. Ask its developer for a specific v2-compatible release.
  4. Rehearse the documented path. Bring the copy of 1.x up to date, follow the official upgrade guide in a separate directory and verify logins, nodes, eggs, server controls and billing callbacks.
  5. Protect rollback. Back up and test restoration of the database, panel files and .env with its APP_KEY. Schedule the real cutover only after the copy passes.

What this means for Pterodactyl addons, including ours

Panel major versions are separate compatibility targets. Our AlwaysMOTD for Pterodactyl 1.x and Security Scanner for Pterodactyl 1.x are not v2 extensions. The separate Graphite Theme for v2, Player Manager for v2 and Security Scanner for v2 target the v2 line. Check each current product listing and its exact beta requirements before installation.

Since then our v2 line has grown to 22 extensions, from Plugin Installer and Version Changer to Backup Manager and Staff Permissions. See them all in the best Pterodactyl v2 extensions, compare themes in the best Pterodactyl v2 themes, and read Pterodactyl v2 vs v1 for the upgrade decision.

The SDK should make extension updates easier, but beta packages can still change. Try official examples on a disposable panel first, then test third-party extensions individually.

If the uncertainty makes you want to look at other panels, we have a Calagopus review and a guide to migrating from Pterodactyl to Calagopus. We would not switch only because of v2, though: its extension API addresses a long-standing complaint about Pterodactyl, which is that customising it means patching code that the next update overwrites.

Run your panel without running the server

BuiltByOtte Cloud hosts and updates your Paymenter or Pterodactyl panel, with nightly backups, monitoring and your own domain. Try the base panel free for 3 days; no card and no automatic charges.

Try BuiltByOtte Cloud free

Related tools

Graphite Theme | Pterodactyl v2 Restyle your whole panel from the admin area. Colors, fonts, logos, and more Pterodactyl v2 · $19.99 Player Manager | Pterodactyl v2 Manage your Minecraft players straight from your Pterodactyl panel Pterodactyl v2 · $10.99 Security Scanner | Pterodactyl v2 Protect your hosting from possible malware and security issues! Pterodactyl v2 · $17.99