So You Want To Get Into SCP
SCP is a collaborative fiction project centered around a fictional secret organization that documents and contains anomalous entities and objects. It started on 4chan's /x/ board in 2008 and grew into one of the largest creative writing communities on the internet. The site is organized as a wiki with thousands of entries, each written in a clinical, bureaucratic style that treats impossible things like routine paperwork. The writing style is deliberately dry. You describe a creature that eats memories the same way a lab report describes a mouse. That contrast between subject and tone is what makes the format work. Beginners often miss that and write horror stories dressed up as documents. It reads poorly. Stick to the clinical voice and let the anomaly speak for itself.
The Mysterious World Of Scp Unveiling The Secrets Of The Fictional Foundation
If you want to understand how this actually functions beyond the surface-level idea, you have to look at the submission process. The main site is SCP Foundation Wiki (scp-wiki.wikidot.com). There are other branches under the SCP Collective umbrella, but the main site has the most mature ecosystem. Creating an account requires email verification and a short waiting period. Then you can draft your own SCP entry. I spent months trying to get a first submission approved through the review process. The review team checks for format compliance, originality, quality of writing, and whether the concept overlaps too closely with existing entries. My first submission got rejected in 45 minutes. Not because the writing was bad, but because the anomaly's containment procedure was functionally identical to an existing SCP with a different number. You learn quickly that the database has been around for over fifteen years and almost every basic idea has already been explored. The workaround I used was to anchor the anomaly to something deeply specific and personal rather than reaching for cosmic horror. I wrote about an object that caused localized temporal stagnation in a single suburban household, told through the perspective of a facilities maintenance worker filing expense reports. It went through revision round two and eventually got approved. The key insight nobody tells you is that the bureaucratic framing matters more than the creature design. Readers accept a poorly designed monster if the paperwork around it feels authentic.
Another thing to understand is the classification system. Objects are rated from Safe to Thaumiel depending on containment difficulty and threat level. Safe does not mean harmless. It means containment is straightforward. Euclid means containment requires active measures and outcomes are somewhat unpredictable. Keter means containment is difficult and failure is likely. Archon and Thaumiel are rarer classifications. Archon means the anomaly is manageable and contained indefinitely. Thaumiel means the anomaly is used to contain other anomalies. These aren't just flavor labels. Reviewers check that your classification matches your containment description. I once saw a submission downgrade from Keter to Euclid after a reviewer pointed out that the containment procedures described were adequate for long-term storage with minimal oversight. The community has developed extensive documentation on how to write properly formatted SCP entries. There are guides on the wiki itself, Discord servers, and subreddits where writers give feedback before submitting. The revision process is iterative. You post a draft, get comments, rewrite, and resubmit. Most approved SCPs go through at least three major revision cycles. The process takes anywhere from two weeks to three months depending on how many problems reviewers find. One counter-intuitive thing about the format: less is almost always more. Readers have reported that the most effective SCP entries leave gaps. An entity whose full nature is never explained generates more engagement than one that gets a comprehensive origin story dumped in a backstory section. The clinical tone works best when the writer trusts the reader to connect dots. Over-explaining undermines the whole premise of a foundation that claims to understand these things.
Get the Full Details
There are real limitations to engaging with this project. The review queue is massive and processing times vary. During peak periods, a submission can sit unreviewed for six to eight weeks. The wiki software (Wikidot) has a steep learning curve for formatting. Tables, object classes, and containment procedure templates follow strict syntax that breaks silently if you get it wrong. Your entire page can render as broken HTML and you won't know why until someone points it out. I learned to use the preview function relentlessly and to keep a local copy of every draft in case the wiki corrupts it during a save. Some people treat the SCP universe as a shared lore database and get deeply invested in continuity across entries. The official stance is that the wiki operates as a collaborative canon, but individual authors are not required to maintain consistency with other stories. This creates friction. You will encounter readers who demand that your entry align with events from a completely different author's SCP number. Ignore that pressure. Write what you want to write. The format exists to support individual creativity, not to enforce a single narrative. If you want to start reading, go to the main wiki and browse the main page featured articles. Sort by kudos (upvotes) to see what the community considers strong entries. Read the top-rated entries from the last two years, not the oldest classics. The writing standards have shifted significantly since 2010. Early SCPs were groundbreaking because the format was new. Today they read as amateurish by current standards. That doesn't make them worthless, but don't use them as a benchmark for what good SCP writing looks like now.
The community also has a separate space for stories that don't follow the document format. These are called "tall tales" or narrative SCPs and they appear in their own section. They can be written in any style. If your strength is character-driven prose rather than cold clinical documentation, the tall tale section is where you should aim. The review standards there are different and many writers never touch the standard SCP format at all. Another edge case worth mentioning: some authors use SCP as a vehicle for personal expression in ways the foundation's clinical tone seems to contradict. There is a well-documented tradition of embedding autobiographical elements into anomaly descriptions. The community generally accepts this as long as the writing meets quality standards. I found my own way into the format through a entry about a containment breach that parallelled real workplace burnout. It wasn't subtle, but it worked. The bureaucratic language gave me a distance I needed to process something I couldn't write directly. Download links don't really exist for SCP content since it's all hosted on the wiki and licensed under CC BY-SA 3.0. You can read everything online for free. The wikidot platform allows you to download individual pages as PDF through browser print functions, though the formatting will be basic. If you want an offline collection, third-party aggregators exist but their quality varies and they sometimes host outdated or unauthorized versions. Stick to the official wiki if possible.
The biggest practical advice I can give is to read before you write. Spend at least a month going through recent approved entries in the category you want to contribute to. Note the structure, the pacing, the way containment procedures are written. Then write something short. A single page entry is easier to get through review than a sprawling multi-section document. The review process is less intimidating when you start small. Most new contributors who succeed did exactly that. They wrote one tight entry, learned from the feedback, and expanded from there. The project rewards persistence more than raw talent.
