For a lightly populated ARK: Survival Ascended (ASA) dedicated server, published empty-world memory ranges run from 7–8.5 GiB for Extinction to 10.5–12 GiB for The Center. Those figures are starting floors, not safe production allocations: connected players, world age, structures, creatures, storage, configuration and mods all increase usage. Ragnarok, Astraeos and Lost Colony have no published numeric values in the cited official table, so size those maps conservatively and measure them under your actual workload.
Playing with friends? Godlike.Host runs hosted ARK: Survival Ascended servers from 10 data-center locations, with free DDoS protection.
Plan on a modern CPU with at least four logical cores per server instance, strong single-thread performance, an SSD (preferably a 1TB NVMe SSD for a practical host), and substantially more memory than the map’s empty-world reading. Running several maps concurrently means adding each map’s observed working set rather than relying on Steam’s client minimums.
As an Amazon Associate I earn from qualifying purchases.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Quick requirements summary
ASA server sizing has four separate parts: CPU scheduling, RAM, storage and the workload created by players and mods. The map table below is the only published numeric baseline in the cited material. It was measured on an empty new world with default settings and no players, so every value should be treated as a floor.
| Map | Empty new-world RAM | Published status | Planning implication |
|---|---|---|---|
| The Island | 8–10 GiB | Numeric range published | Allow additional memory for players, an older save, builds, creatures and mods. |
| The Center | 10.5–12 GiB | Numeric range published | Largest published empty-map footprint here; leave substantial headroom on the host. |
| Scorched Earth | 7.5–9 GiB | Numeric range published | The empty map is smaller than The Center, but a busy or modded world can still grow considerably. |
| Aberration | 8–10 GiB | Numeric range published | Use the upper end as the starting point when planning a real server. |
| Extinction | 7–8.5 GiB | Numeric range published | Lowest published range, not a guarantee of low usage after the world develops. |
| Ragnarok | Not stated | No numeric value published | Do not substitute a guessed figure; reserve conservatively and measure the running instance. |
| Astraeos | Not stated | No numeric value published | Use observation from your own save and mod set before committing to a tight host plan. |
| Lost Colony | Not stated | No numeric value published | No numeric value is established in the cited table; plan for headroom rather than an estimate. |
GiB (gibibytes) is the unit used by the map table. A host’s operating system, monitoring tools, file cache and other services also consume memory, so a machine with exactly the map’s listed number will not have a usable safety margin.
#1 Best Overall
- This product has been replaced by our latest generation. Please search for the SANDISK Optimus GX 7100 NVMe SSD
- HIGH-OCTANE GAMING. Experience speeds up to 7,250MB/s read and 6,900MB/s write (1-2TB models), with up to 35% faster performance than previous generation.
- PURPOSE-BUILT. Designed for serious on-the-go gamers, with a PCIe Gen4 interface and SANDISK’s next generation TLC 3D NAND.
- MORE TIME TO CLEAR THAT CHECKPOINT. Built with laptops and handheld gaming devices in mind, with up to 100% more power efficiency over the previous generation.
- DO MORE WITH DASHBOARD. Ensure your drive is optimized for prime performance with the downloadable WD_BLACK Dashboard (Windows only).
Why the map figures are only a starting point
Players and world age
Every connected player adds active state, inventories, locations and network activity. A new world with no players is therefore the least demanding case. As a save ages, more areas are explored and more state is retained, so memory can rise even when the current player count is modest.
Structures, creatures and storage
Large bases, industrial machines, tames, wild-creature activity, containers and accumulated storage all add objects the server must keep available. Two servers on the same map can have very different working sets because one may be a fresh cooperative world while the other contains months of construction and breeding.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsSettings, mods and respawn activity
Configuration changes can alter the number and behavior of entities. Mods add their own assets and runtime state. Usage can also fluctuate during creature respawn, so a single idle reading can miss a temporary peak. Capture memory during normal play and during known busy events instead of sizing from an empty server screenshot.
CPU requirements for an ASA dedicated server
Four logical cores per instance
The ARK Official Community Wiki recommends four logical CPU cores for each ASA server instance. Treat that as a per-instance planning rule: a host running three maps concurrently should have enough scheduling capacity for three instances, plus the operating system and any other services. Logical cores are not the same as a promise of equal performance from any processor; clock speed, architecture and contention still matter.
Rank #2
- Ideal for high speed, low power storage
- Gen 4x4 NVMe PCle performance
- Up to 6,000MB/s read, 4,000MB/s write
- Includes Acronis cloning software
- 5-year limited warranty
Prioritize single-thread performance
Gameplay work, apart from physics, largely runs on one thread. A processor with strong per-core performance therefore matters more than simply buying the highest possible core count. Extra cores can help a multi-map host run several instances without contention, but they do not replace a fast main thread for one busy map.
Physics is the exception
Physics can use additional parallel work, which is why four logical cores remains a baseline rather than a complete performance specification. Heavy construction, creature interactions or other physics-intensive scenes may stress the processor differently from a quiet base. Select a recent CPU with high single-core performance and leave capacity for simultaneous instances.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallHow to size RAM for one map
- Identify the map. Start with the published empty-world range. For a map without a published numeric value, there is no defensible numeric baseline in the cited table, so use a deliberately generous allocation and validate it empirically.
- Use the upper end of the range. For example, plan from 10 GiB for The Island, 12 GiB for The Center, 9 GiB for Scorched Earth, 10 GiB for Aberration and 8.5 GiB for Extinction before adding anything else.
- Add host overhead. Reserve memory for the operating system, the server process’s transient peaks, save operations, logs, updates and monitoring. A map value is not the amount you can safely assign to the entire machine.
- Account for the real workload. Estimate peak concurrent players, the expected age of the save, construction density, creature count, storage and mod load. Use the busiest realistic period, not an overnight idle period.
- Validate after launch. Watch the server process and total host memory while players join, travel, build, fight and trigger respawns. Increase the allocation if the host approaches exhaustion or begins paging.
As a sanity check, a 12 GiB empty-world reading for The Center leaves only about 4 GiB on a 16 GiB machine before the operating system and any workload growth. That arithmetic explains why the Steam client’s 16 GB minimum is not a dedicated-server recommendation. A 32 GB host may be workable for one lightly populated map, but it is not a guarantee for an old, heavily built or modded world.
Planning a multi-map cluster
When several maps run at the same time, add the observed working set of each active instance. Do not choose the largest map’s figure and assume the other maps are free. A useful planning expression is:
Rank #3
- PCIe 4.0 Performance: Delivers up to 7,100 MB/s read and 6,000 MB/s write speeds for quicker game load times, bootups, and smooth multitasking
- Spacious 1TB SSD: Provides space for AAA games, apps, and media with standard Gen4 NVMe performance for casual gamers and home users
- Broad Compatibility: Works seamlessly with laptops, desktops, and select gaming consoles including ROG Ally X, Lenovo Legion Go, and AYANEO Kun. Also backward compatible with PCIe Gen3 systems for flexible upgrades
- Better Productivity: Up to 2x faster than previous Gen3 generation. Improve performance for real world tasks like booting Windows, starting applications like Adobe Photoshop and Illustrator, and working in applications like Microsoft Excel and PowerPoint
- Trusted Micron Quality: Built with advanced G8 NAND and thermal control for reliable Gen4 performance trusted by gamers and home users
Total host RAM = map A working set + map B working set + … + operating-system headroom + workload and update reserve.
For example, a cluster containing The Island and The Center should begin with both maps’ measured usage, not just The Center’s 10.5–12 GiB floor. If each world is busy, their peaks can overlap. Add further reserve for mod loading, save writing, logs and player activity, then test the cluster with all instances online. A map without a published numeric value should be treated as an uncertainty that requires more headroom, not as zero in the calculation.
| Cluster situation | What to measure | Capacity decision |
|---|---|---|
| One lightly populated map | Peak process memory during joins, travel and saves | Start above the map’s upper empty-world value and keep host memory available for growth. |
| Two or more maps online | Peak working set of every instance at the same time | Sum the peaks, then add operating-system and maintenance reserve. |
| Mod-heavy cluster | Memory during mod initialization and normal play | Use the measured modded footprint; an empty vanilla reading is not representative. |
| Long-running mature saves | Usage after the busiest bases and creature populations are present | Size for the mature save, not the first-day world. |
Storage: installation, saves and SSD choice
One ASA server installation is about 11 GiB. That is only the program installation. The host also needs space for world saves, player and tribe profiles, logs, updates and mods. These files grow and change over time, and updates may require temporary working space, so a disk sized to exactly 11 GiB will fail quickly.
An SSD is required for the game client, and the same storage class is sensible for a dedicated server. Prefer a modern NVMe SSD; the strongest supported capacity phrase in the available guidance is 1TB NVMe SSD. A larger disk is useful when several maps, backups and mod collections share the machine. Keep free space available for updates and retained backups rather than filling the volume with active saves.
Rank #4
- HUGE SPEED BOOST: Get random read/write speeds that are 40%/55% faster than 980 PRO; Experience up to 1400K/1550K IOPS, while sequential read/write speeds up to 7,450/6,900 MB/s reach near the max performance of PCIe 4.0*
- BREAKTHROUGH POWER EFFICIENCY: Use less power and get more performance; Enjoy up to 50% improved performance per watt over 980 PRO, plus optimal power efficiency with max PCIe 4.0 performance**
- SMART THERMAL CONTROL: Samsung's own nickel-coated controller delivers effective thermal control; With its slim size, 990 PRO is a perfect fit for desktops and laptops that meet the PCI-SIG D8 standard***
- THE CHAMPION MAKER: Up to 65% improvement in random performance enables faster loads for an ultimate gaming experience on PS5 and DirectStorage PC games****
- SAMSUNG MAGICIAN SOFTWARE: Get the most out of your SSD with Samsung Magician's advanced yet intuitive optimization tools; Monitor drive health, protect valuable data, and receive important updates for your 990 PRO
What to place on the fast disk
- Each server installation and its map files.
- Active world saves plus player and tribe profiles.
- Mods and their update cache.
- Logs and temporary update files.
- Backups stored separately when possible, so a full or failed primary volume does not remove the only copy.
Client requirements versus dedicated-server sizing
Steam lists the following requirements for running the ASA client on Windows 10 or 11: a Ryzen 5 2600X or Core i7-6800K class processor, 16 GB RAM minimum, 32 GB recommended, DirectX 12, broadband internet and 180 GB of storage. Steam explicitly says SSD Required. Those figures describe the player’s local game, not a complete rule for a headless dedicated server.
| Steam client item | What it means for server planning |
|---|---|
| 16 GB RAM minimum | Not a safe allocation for a production server; it leaves little room above a large map’s empty-world footprint. |
| 32 GB RAM recommended | A client recommendation, not a promise that every map, save and mod set fits on a 32 GB server. |
| 180 GB storage | Client capacity guidance; a server also needs saves, profiles, logs, mods, updates and backups. |
| Windows 10/11 and DirectX 12 | Client-platform requirements; they do not define the CPU, memory or storage envelope of every server operating system. |
| Broadband internet | A connectivity requirement for play; server bandwidth and latency still depend on player count and hosting conditions. |
The developer describes ASA as being built on a newer Unreal Engine 5 technology stack and notes that systems were still being worked through during development. That context is another reason to retain operational headroom and test updates before applying them to a busy production world.
Free tools Windows power users keep installed
One-click scans. No signup required.
Map-by-map planning notes
The Island: 8–10 GiB empty
The Island’s published range is 8–10 GiB for a new, empty, default-settings world. Use 10 GiB as the baseline for capacity planning, then add the host and workload reserve. A mature base-building community can exceed the empty reading through structures, tames, inventories and accumulated save state.
The Center: 10.5–12 GiB empty
The Center has the largest published empty-map range in this table. Its 12 GiB upper value should be considered before player and mod growth, making tight 16 GB hosts especially unsuitable. Measure peak usage after players establish bases and move between regions.
Best Value
- SPEED UP PROJECTS. Launch creator applications fast with uncompromising PCIe 4.0 read speeds up to 7,100MB/s,[2] (1TB and 2TB[1] models) and write speeds up to 6,700MB/s[2] (1TB[1]-4TB[1] models).
- CREATE AND STORE MORE. Make more room for your 4K videos and high-resolution images with capacities from 500GB[1] up to 4TB[1] on M.2 2280 built with our trusted 8th generation SANDISK BiCS QLC 3D CBA NAND.
- IT GOES WHERE YOU GO. With an all-new power efficient design, your drive delivers high performance with low power, giving you more time to be productive while on the go.
- UNCOMPROMISED RELIABILITY. With up to 1,200 TBW[3] (4TB[1] model) endurance rating, your drive is designed for creators.
- KEEP YOUR DRIVE UPDATED. Monitor your SSD’s performance and check for updates with the downloadable SANDISK Dashboard application.[5]
Scorched Earth: 7.5–9 GiB empty
Scorched Earth starts lower than The Island and The Center in the empty-world table. That difference is not a fixed operating cost: structures, creatures, save age, configuration and mods can erase the apparent advantage. Plan from 9 GiB, not from the lower endpoint.
Aberration: 8–10 GiB empty
Aberration’s range overlaps The Island’s. Use 10 GiB for the initial model and verify it with the intended player population and mod set. The map’s lower empty value should not be used to justify a host with no spare memory.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Extinction: 7–8.5 GiB empty
Extinction has the smallest published empty-world footprint at 7–8.5 GiB. It still needs headroom for the operating system, long-running saves and activity. Treat 8.5 GiB as the starting floor for a real deployment.
Ragnarok, Astraeos and Lost Colony: numeric values are not published
The cited official table lists these maps without numeric RAM ranges. No responsible sizing rule can turn that label into a precise number. Start with more capacity than a known small map would require, run the intended configuration, and record actual peak working sets before reducing the allocation or packing additional instances onto the host.
Quick Recap
Common sizing mistakes and fixes
- Using the 16 GB client minimum: Replace it with the map’s upper empty-world value plus operating-system and workload headroom.
- Adding only installation sizes: Include saves, profiles, logs, mods, updates and backups in the storage plan.
- Counting physical cores instead of logical cores: Apply the four-logical-core-per-instance guidance and account for other instances competing for CPU time.
- Buying many slow cores for one map: Favor strong single-thread performance because most gameplay work is concentrated on one thread.
- Sizing from an empty test world: Test mature saves, peak player counts, large bases, creature activity and mod initialization.
- Treating maps without published values as known quantities: Measure them under your own workload and retain extra capacity until you have stable observations.
- Filling the SSD: Keep free space for updates, logs and saves; a full volume can interrupt writes even when the game itself is installed correctly.
Pre-launch capacity checklist
- Record the map or maps and whether any lack published numeric values.
- Write down the published upper empty-world value where one exists.
- Count concurrent instances and confirm four logical CPU cores per instance can be scheduled alongside the host operating system.
- Choose a modern, high-single-thread-performance CPU and NVMe SSD storage.
- Reserve RAM for the operating system, saves, logs, updates, players, structures, creatures and mods.
- Install enough disk capacity for the approximately 11 GiB installation plus all data and free update space; 1TB NVMe SSD is a practical supported target.
- Load-test with realistic players and mature-world activity, monitor peak memory and CPU, and expand before the host begins paging or starving an instance.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
