SCP: Secret Laboratory Roadmap 2026: Megapatch III, SCP-953 & What Hosts Should Plan For

SCP: Secret Laboratory’s 2026 roadmap: Northwood’s Megapatch III work towards 15.0, the SCP-953 implementation, the new Surface Zone, and what community-server owners should plan around.

Where Northwood Studios Communicates

Northwood Studios posts patch releases to Steam News and detail work to a monthly Patreon post, which is then mirrored to Steam. The Patreon posts are where the real roadmap lives. The June 2026 “Megapatch III Progress Report” is a mirrored March Patreon post, so the Steam feed runs a few months behind the actual development chatter. Feature reveals get their own trailers.

Where the Game Stands

Stable and free-to-play, on version 14.2.7, with development split between small maintenance patches and a long-running major release. Northwood is explicit about the split: 14.2.7’s own notes say they are “still hard at work developing the main features for 15.0” and are “dropping some small fixes in the meanwhile.” For a server owner that is the healthiest possible pattern, because the live build keeps getting fixed while the big one bakes.

What’s Confirmed for 2026

• SCP-953, revealed 14 February 2026 with its own trailer. A demon-fox SCP from an ancient bloodline, described by Northwood as “a new evil unleashed in Site-02 this year”.
• SCP-953 implementation is the programming team’s main focus (Progress Report, 26 June 2026). Lead programmer Beryl is building the code and systems ahead of the model and animations so the two can be joined late, a deliberate choice to speed the update up.
• Lockers, generators and warhead panels: models finished, implementation in QA, and Northwood says they are confident these land in 15.0.
• Surface Zone layout complete. Level Design has moved on to the Gate A and Gate B Entrance Zone rooms, specifically to avoid creating a choke point that would undo the new Surface Zone’s anti-camping design.
• 14.2.7, 30 May 2026: voice-chat fix, Anti-SCP-207 AHP fix, SCP-1509 revive fix. Preceded by 14.2.6 on 25 March and the Anniversary Patch on 7 January.

Not confirmed: there is no announced release date for Megapatch III / 15.0, and no public list of everything it contains. Anything you read with a date attached is a guess.

What Server Admins Should Plan For

Hardware

SCP:SL is a round-based FPS, so the load is spiky rather than steady: an empty lobby costs nothing and a full round with a plugin stack saturates one fast core. Single-thread speed matters far more than RAM.

• Private facility for a Discord, ~20 slots → Plan S (4 GB)
• Listed community server, ~30 slots → Plan M (6 GB)
• Public 50-slot with a full plugin loadout → Plan L (8 GB+)

Plan for 15.0 rather than for today. A new SCP with its own systems, plus a redesigned Surface Zone and Entrance Zone, adds simulation work to exactly the moment when a round is already busiest. Full detail in CPU, RAM and slot planning.

Patch-day hygiene: the release chain

SCP:SL punishes a careless update harder than most games, because a modded server is three versions that all have to agree: the server build, the framework (LabAPI or EXILED), and every plugin. Update in that order, never in parallel:

• Back up config, plugins and the server directory before touching anything.
• Update the server build first, and only then install framework and plugin versions known to support it.
• Start with no public players and read the log for load failures, then run one private round before reopening.

The symptom tells you the layer: everyone rejected means a client/server build mismatch; stock server fine but modded server dead means the framework or a plugin. Both are covered in updating safely after a patch and installing EXILED plugins. When 15.0 finally lands, expect the whole plugin ecosystem to need rebuilding. That is the normal cost of a megapatch, and it is worth having a rollback ready.

Bottom Line

SCP:SL in 2026 is a game with a real, visible roadmap and no dates on it. Megapatch III is coming, SCP-953 is its headline, and Northwood keeps the live build patched while it works. For community-server owners the whole job is the release chain: server build, then framework, then plugins, with a backup taken before the first step. Get that routine right and 15.0 is an evening’s work instead of a lost weekend.