Pterodactyl Eggs: Download, Import, Create & VPS Guide
Understand what Pterodactyl eggs do, find maintained game and application eggs, import the JSON safely, and choose a server that can run them reliably.
Quick answer
Pterodactyl eggs are JSON blueprints that define a server's Docker image, install script, startup command, variables, files, and stop behavior. Download a maintained egg, then import it in Admin → Nests → Import Egg and create a test server from it. The egg does not provide compute: if the old setup depends on a gaming PC that must stay awake, a residential address and router, or a managed host with fixed templates, a VPS gives Pterodactyl an always-on Linux node, public IP, chosen CPU and RAM, root access, scheduled backups, and room for several isolated game or application eggs.
What are Pterodactyl eggs?
A Pterodactyl egg is an importable JSON blueprint that tells Pterodactyl Panel how to install and run a specific game server or application inside a container. Eggs are grouped into nests. The egg supplies the software recipe; the Pterodactyl node supplies the CPU, memory, storage, network, and uptime.
Docker image
Chooses the container runtime, such as a Pterodactyl Yolk for Java, Node.js, or a SteamCMD game.
Installation script
Downloads server files and prepares the directory when a new server is installed or reinstalled.
Startup command
Turns panel variables such as memory, port, version, and executable name into the command that starts the service.
Configuration rules
Defines editable variables, stop commands, log paths, config-file parsers, and other behavior exposed in the panel.
{
"docker_images": { "Java 21": "ghcr.io/..." },
"startup": "java -Xmx{{SERVER_MEMORY}}M ...",
"config": { "startup": {}, "stop": "stop" },
"scripts": { "installation": { "script": "..." } },
"variables": [ ... ]
}How to download and import a Pterodactyl egg
Use the maintained community catalog for Pterodactyl game eggs, application eggs, and generic language eggs. It covers common searches such as Minecraft, Terraria, Node.js, Python, bots, databases, and SteamCMD servers.
- 1
Find a maintained egg
Find the game or application in the official community catalog. Open its details and read the notes for supported versions, architecture, ports, and required files.
- 2
Download the egg JSON
Download the egg JSON. Keep the file name and source URL with your server notes so a future update is easy to trace.
- 3
Import the egg into a nest
Open Pterodactyl Admin, choose Nests, select the matching nest, and use Import Egg. Create a separate nest first when the egg does not belong in an existing group.
- 4
Review the runtime and variables
Review the imported Docker image, startup command, variables, and default allocation. Save the egg, then create a test server from it.
- 5
Create and test a server
Run the installation once, watch the console until the ready message appears, connect on the assigned port, and take a backup before changing versions or mods.
Updating an egg without risking a live server
Export the current egg and back up the server first. Compare the new JSON for image, startup, variable, and install-script changes, import it as a new version, then test a copied server before moving the production allocation. That preserves a known-good rollback path.
Pterodactyl nest vs egg vs Docker image
| Term | What it does | Examples |
|---|---|---|
| Nest | A category that groups related server templates. | Minecraft, Source Engine, voice servers |
| Egg | The JSON blueprint for installing, configuring, starting, and stopping one server type. | Paper, Terraria, Rust, Node.js |
| Yolk / Docker image | The container environment that provides the operating-system packages and runtime. | Java 21, Node.js 22, Wine, SteamCMD |
| Allocation | An IP-and-port pair assigned to a server on a Pterodactyl node. | 203.0.113.20:25565 |
Pterodactyl egg compatibility checklist
Four details explain most failed installs and unreachable servers. Read them once before creating the server so the first run produces useful logs and a reachable endpoint.
| Check | What to match | Value |
|---|---|---|
| Game and release | The egg names the server build and exposes a version variable or a maintained download source. | Prevents an old installer from fetching a removed release or starting the wrong binary. |
| Image and CPU architecture | The Docker image supports the node architecture and contains the required Java, Node.js, Wine, or system libraries. | Avoids an install that completes but cannot execute the server process. |
| Ports and allocations | Every game, query, RCON, voice, and file-transfer port has a matching allocation and firewall rule. | Keeps the panel, container, host firewall, and player join address on the same port numbers. |
| Memory, disk, and files | The node has room for the game, world, logs, updates, backups, and the memory limit expected by the startup command. | Gives the installer and live server enough working space without changing the egg later. |
Why run Pterodactyl eggs on a VPS?
The egg is free, but it is not a host. A VPS is the natural purchase when the old setup depends on a gaming PC, a residential connection, or a panel that restricts server templates. The VPS provides the always-on Linux node, public address, root access, storage, and resource pool that make Pterodactyl useful across several games and applications.
Old setup
Run the node on a gaming PC at home
The panel and every egg stop when the PC sleeps, game workloads compete for the same CPU and memory, and remote players depend on the home connection.
A VPS keeps Wings and its game containers online on separate compute, with a stable public address for the panel and allocations.
Old setup
Stay inside a fixed game-host catalog
A managed game host can limit the templates, Docker images, startup variables, files, and scheduled jobs available to the account.
Root access lets one Pterodactyl node import maintained community eggs, use custom eggs, schedule backups, and move standard files between servers.
Old setup
Create a separate plan for every experiment
Bots, proxies, test worlds, and small game servers become separate subscriptions even when their combined resource use is modest.
One correctly sized node can run several isolated eggs and divide CPU, memory, disk, and ports through the Pterodactyl panel.
Pterodactyl VPS sizing by egg workload
These are practical starting ranges, not hard limits. Leave capacity for Ubuntu, Docker, Wings, the panel database, and backups; then resize from real CPU, memory, disk, and tick-time measurements.
| Workload | Starting size | Good fit |
|---|---|---|
| Bot, proxy, or small language egg | 1–2 vCPU · 2 GB RAM · 40 GB SSD | A light Node.js, Python, proxy, or test service. |
| Small vanilla game server | 2 vCPU · 4 GB RAM · 80 GB SSD | A private Minecraft, Terraria, or similar server with a small group. |
| Modded or 10–20-player server | 4 vCPU · 8 GB RAM · 120 GB SSD | More world activity, plugins, mods, or a heavier SteamCMD title. |
| Several active eggs | 4–8 vCPU · 16 GB+ RAM · 200 GB+ SSD | Multiple game servers plus the panel, database, backups, and monitoring. |
Use SSD storage
World saves, SteamCMD updates, container layers, logs, and local backups all share the node disk.
Place the node near players
Choose the region that minimizes the common route for the group, not simply the city nearest the administrator.
Separate busy workloads
Move a heavily modded or high-tick server to its own node when it begins competing with otherwise stable eggs.
Best servers for Pterodactyl eggs
Choose Vultr first for a general Pterodactyl deployment with broad automation documentation and a simple growth path. Choose DMIT when Los Angeles, Hong Kong, or Tokyo routing is the reason for the server location. Both are self-managed servers, so the panel, Wings, eggs, and backups remain under your control.
Vultr
- 80M+ cloud server instances launched
- Official API, CLI, and Terraform documentation
- Published hourly billing with a monthly cap
- Public status pages for regional service history
DMIT
- Los Angeles, Hong Kong, and Tokyo locations
- Published 3.8 Tbps aggregate Tier-1 capacity in Los Angeles
- 99% service-level commitment with account credits
- Eligible new orders have a three-day refund window under 30 GB
Pterodactyl eggs FAQ
Continue your server setup
Official Pterodactyl references
These official project sources cover the maintained egg catalog, GitHub repositories, custom egg format, and the panel setup that creates nests and eggs.