How The SCP Foundation Wiki Actually Works Under The Hood
The SCP Foundation is a collaborative fiction project centered on a secret organization that contains anomalies. Most people find it through Reddit or the main wiki at scp-wiki.wikidot.com. The site has been around since 2008 and contains thousands of documents, each following a rough template. I have spent years reading, contributing, and organizing information from these articles, and what you will find there is not a single unified canon but a sprawling collection of competing ideas about how a global black-budget organization would function. The core mechanic that makes SCP useful as a reference framework is containment procedure design. Each article describes an anomaly, its properties, and how the Foundation manages it. The more detailed and internally consistent a document is, the more usable it becomes for writers, game designers, or researchers building their own fictional systems. I learned this the hard way when a client asked me to extract containment logic from about forty SCP articles to build a simulation. The problem was that containment procedures are written inconsistently across the wiki. One article might describe a physical lock mechanism in detail while another describes the same type of object using purely abstract language about "reality-bending fields." My workaround was to build a spreadsheet mapping every physical containment step mentioned across all articles, then cross-reference them with real-world analogs. Items that had no analog were flagged separately. This let me separate articles that could ground a simulation in real engineering from those that required pure speculative rules. The whole process took about three days for forty articles, which is faster than most people realize once you know the pattern.
Classification Systems And What They Actually Mean
SCP objects use a classification tier system. Safe, Euclid, Keter, and Thaumiel are the four main categories you will see most often. These are not ratings of danger level. They are ratings of predictability and containment difficulty. Safe does not mean harmless. It means the object behaves in a predictable way when interacted with under normal conditions. Keter means the object resists containment or its behavior changes based on unknown variables. Euclid sits between the two. I have seen writers treat Safe as a green light and Keter as a red light, which is wrong. A Safe class object can kill you instantly if you touch it. Euclid class objects are the ones that cause the most narrative problems because you never quite know what they will do next. The distinction matters if you are building your own fictional framework around anomaly containment.
Building Your Own Containment Framework
If you want to create a system modeled after SCP methodology, start with a behavior profile for each anomaly. Document what it does, how often it does it, what triggers it, and what stops it. Then write containment steps in order of physical sequence, not importance. Most people write the most dramatic step first. That approach breaks down when you need to hand the document to someone who has never seen the object before. The standard format most contributors follow includes an item number, object class, containment procedures, description, and sometimes addenda like incident reports or interview transcripts. Addenda are where the real world-building happens. A containment procedure tells you how to lock a door. An addendum tells you why the door needed locking in the first place.
Get the Full Details
Common Pitfalls Beginners Make
The biggest mistake is treating the SCP Foundation as a factual reference. It is not. It is fiction. Some articles reference real-world physics or biology and twist them slightly, but many are outright fantasy dressed in clinical language. If you quote SCP data in a serious context, you will get corrected frequently. Another issue is over-indexing on the gore or horror elements. The website has plenty of disturbing content, but the structural work—the taxonomy, the classification system, the containment logic—is what makes the project durable. The horror is secondary to the organizational framework.
Where To Find The Source Material
The main wiki is at scp-wiki.wikidot.com. The English archives at archives.scp-wiki.net hold older articles no longer featured on the front page. Reddit communities like r/SCP and r/CobaltSiege discuss interpretations and alternate universes. For more experimental formats, check out scp-wiki.wikidot.com/scp-series which organizes documents by series and tone. There is no official download package. The wiki is community-maintained and any export tool you find online is unofficial. I used a Python script with the wikidot API to pull raw markdown for personal research, but that was for internal analysis only. I would not recommend redistributing exported content without checking licensing terms for each article individually.
Limitations Of The SCP Framework
The classification system does not scale well beyond individual anomalies. If you are managing a site with hundreds of objects, the Safe-Euclid-Keter model becomes useless because the labels stop carrying meaningful information. Some contributors have proposed additional tiers like Neutralized or Apollyon, but these are not universally adopted. The system works best for small-scale documentation and breaks down at scale. The clinical writing style that defines SCP also limits accessibility. Articles assume familiarity with military and scientific jargon. If you are new to the format, you may find many articles difficult to parse on first read. The addenda often help, but they are not present in every article. For organizations looking to build a similar fictional universe from scratch, the SCP model is a solid starting point but not a complete solution. You will need to adapt the classification system for your own purposes and decide whether to adopt the clinical tone or diverge from it. The project remains valuable primarily as a reference for how to structure anomaly documentation consistently across a large collaborative effort.
