Sandbox:Big Rules Page


This is a sandbox page.

It is not approved or active policy. It is a draft, and as such, may be incomplete.

This page lists all major SCP wiki rules, and how warnings and bans work. Follow the spirit of the rules, not just the exact letter.

Table of Contents

Rule Zero

Don't be a dick.

This is the foremost rule from which most other rules follow. We expect you to behave in a reasonably civil, mature, and non-disruptive way on the SCP wiki.

I. Interaction & Behavior

  1. Voting: You may vote on any article on the site for any reason you like, as long as your reasoning is based solely on the content of the article.
    1. Voting on your own article: You can upvote or even downvote your article as you like.
    2. Brigading: Calling for group downvoting (or group upvoting) of an article is prohibited. Being part of a vote brigade may lead to a ban.
      • Note: Not every call to check out an article by someone who dislikes it is brigading. Context and intent will determine whether or not an incident is considered brigading. Rule of thumb: Don't try to push a group of people to vote the same as you.
  2. Comments: You can comment almost anywhere on the site1, as long as you are respectful to other users. All comments must follow the Criticism Policy. Do not troll or make personal attacks.
    1. Arguments: You may dispute the actions and opinions of anyone, including staff, as long as you do it in a calm, mature, and civil way.
  3. Forum Activity: Don't make contentless or excessively short posts (spam), don't bump threads for attention, and don't post on threads more than a few months old if you're not contributing substantially to the conversation.
    • The SCP Wiki is an inclusive environment. Hate speech and slurs will not be tolerated.
    • Avoid double posting. Edit your previous posts using the "edit" function under the "options" tab to the lower right of every comment.
    • Every image posted to forum or discussion threads must be collapsed (check the "Formatting" tab of this guide for the code for collapsibles).

II. Site Content

  1. Posting Articles: Do not post a large number of low-quality articles. When staff tell you to slow down or stop posting, listen.
  2. Using images: Images included in your article must follow the rules of our Image Use Policy. You must include the source of your images on the discussion page, and this source must comply with our site policy and license. If you have any questions, contact the Licensing Team.
  3. Plagiarism: You may not copy any portion of someone else's writing to use as your own work without proper attribution. You may not attempt to pass off another user's article as your own work. Doing so will result in summary deletion of the work.
    • Note: Borrowing narrative or character content from other works is generally fine, so long as there is not a blatant or malicious attempt to deceive the reader into believing that the work is your own. For example, consider the numerous adaptations of Sherlock Holmes: Elementary, Sherlock, The Great Mouse Detective, etc. Your works should be original in style and technique. Contact staff if you're not certain if something is plagiarism.
    • Because plagiarism is both a licensing issue and a violation of site rules, we have a special Plagiarism Jurisdiction policy.
    • The sole exception to this is non user facing content2, users are allowed to take CSS and other formatting elements from other user's articles. Requesting permission or giving credit for such content is not required, though we do recommend a mention of any works that you have taken CSS code from . All CSS must still comply with the technical content policy.
  4. Collaborative Posting:
    1. All posted works must be written by the user that posts the work unless specifically noted as being a collaboration between one or more site users that are current members of the SCP-Wiki at the time of publication. Collaborative works must indicate which site users collaborated in the creation of the article in question.
    2. Surviving articles that are improperly attributed will be given a grace period of 48 hours from notification, where the poster will be given the opportunity to provide correct attribution. After the expiration of that timer, articles that have not been corrected will be subject to summary deletion, regardless of vote count.
    3. Failure to abide by this policy will result in disciplinary action, according to the usual escalation procedures.
    4. This does not exempt articles from deletion via the standard voting process, should downvotes exceed stated thresholds.
  5. Content Posting by Banned Users: Users currently banned from the site may not submit new articles or other works to the site in any way. Users banned for harassment concerns may not request content edits to their articles or submit any new content to the site in any way.
    1. Users banned for disciplinary matters may request content edits to existing work so long as proposed edits are not intentionally provocative, rule-breaking, or be so universal as to constitute a de facto new piece. Proposed edits will be considered on a case-by-case basis with no guarantees of acceptance. Attempts to circumvent this policy will be seen as justification to deny any future edit requests.
    2. All banned users may request deletion of their existing work or works, within reason and at staff’s discretion.
  6. Editing:
    1. Responding to edits of your articles: You may alter the text of your own articles at will. However, please do not remove technical changes to your articles, such as an added rating module or a corrected page name. (See also: technical-content-policy)
    2. Editing others' articles: You may correct unintentional grammar, spelling, or formatting errors on other peoples' articles. Please put a summary of changes in the 'Short description of changes' box. Any further edits require permission from the original author, the current curator, or the Curation team. Any unauthorized edits may be viewed as vandalism and subject to disciplinary action.
    3. Collaborative logs: You are free to add original content to open collaborative logs. These pages are tagged as "collaboration". Content may be removed by the page owner or the Curation team. Please do not fix unauthorized or bad edits — contact the original owner or Curation about additions that you feel are inappropriate or low-quality. Alterations to the structure of a collaborative log are not permitted.
    4. Updating tags: Don't add or change tags unless you know what you're doing. If you have any questions about implementing new tags, please contact a member of the Technical Team. If you have any questions about the tagging process in general, please contact a member of MAST. Do not remove Staff Process tags from any article (in-rewrite, deletion-range, deletable, _cc, or _image).
  7. AI-generated content
    1. The use of generative3 machine learning4 models to generate user facing content5 is banned.
      • Users who post AI-generated content to the SCP wiki will receive a revocation of membership on their first offense, and a permanent ban on the second.
      • Good faith exception: This policy does not apply to properly-cited images from external sources unless they were created by, for, or at the behest of the user who posted them to the Wiki.
    2. Furthermore, the usage of tools whose primary use is generative machine learning is also banned for user facing content.
    3. All exceptions to this policy are on the following white list:
      1. (This list is currently empty)
    4. Examples of banned content include but are not limited to
      1. ChatGPT-generated text
      2. Midjourney/Stable diffusion
      3. AI voice generation
    5. Examples of allowed content
      1. DeepL translator, Grammarly (proofreading/spellcheck assistance only. No AI-generated content or AI-revised/rewritten material)
      2. Fractal generation
      3. Traditional text to speech (if license compatible)
      4. AI-generated CSS code
      5. Writing stories about AIs
  8. Donations: Read and follow donations-policy.

III. Interacting With Staff

  1. Moderative Posts: If you see a "Staff Post", "Mod Post", or "Admin Post", do not reply except in the following circumstances:
    1. Call for Rewrite: Only reply if you want to volunteer to rewrite the page, or to discuss the rewriting of the page.
    2. Deletion Vote: Only reply if you want to ask to rewrite the page, or to request a stay of deletion.
    3. Open: Anyone may respond to this post.
  2. Staff Requests: If a staff member asks you to change your behavior, whether by Private Message, Staff post, or other means, you are expected to do so.
  3. Ended Discussions: Do not try to continue a conversation that has been given a Stop Order.
  4. Staff Decisions/Appealing: If you disagree with a Staff decision, you may appeal to a different staff member. The decision of the other staff member is the final decision on the issue.

IV. Disciplinary Process

The normal steps of punishment escalation are as follows:

  1. Warning
  2. Membership Revocation
  3. Short Ban (usually week-long to month-long)
  4. Long Ban (month-long to year-long)
  5. Permanent Ban

If a staff member warns you about your behavior, and you do not follow the instructions they give you, you will be revoked or banned.

Additional violations equal longer bans. Especially severe violations may result in skipping to more severe punishments, including being permanently banned immediately.

Users who receive permanent or year-long site or chat bans can have their cases reviewed by the chatop team or site disciplinary team respectively, who may decide to enact disciplinary measures if they feel it is warranted.

After your ban has been served, you will have to reapply for site membership. If you want to rejoin the community, you must follow the same process as all new members.

These actions will never result in banning:

  • Writing an article no one likes.
  • Voting on any article based solely on your own opinion of its quality or merits.
  • Respectful disagreement with users or staff decisions.

These actions can result in an immediate permanent ban:

V. Appeals

Any user that has received a site ban lasting longer than 24 hours is granted an opportunity to appeal that ban immediately. They may, at their discretion, choose to wait as long as they wish to appeal the ban or waive the appeal opportunity entirely. Users who have been banned for longer than a year are granted an additional opportunity to appeal upon the anniversary of the initial ban date. Users that have been permanently banned may appeal annually until such a time that the Disciplinary team decides to revoke their appeal privileges.

Exceptions to this are as follows:

  • Users who have been banned for being underage may not appeal unless the judgment was made in error. This ban cannot otherwise be overturned until user has reached minimum age requirements.
  • Users who have been banned for blatant severe trolling may never appeal.
  • Users who attempt to hack, exploit, or otherwise gain control of or damage SCP Wiki-related servers or accounts may never appeal.
  • Certain anti-harassment bans may never be appealed.
  • Users who have had their appellant privileges revoked may never appeal. In other words - you can lose your ban appeal privileges in certain circumstances.

Chat bans are usually separate from site bans and do not always mirror each other. An exception to this is that someone permanently banned from the site may be permanently banned from the chat as well. This does not apply in the reverse, however. Chat permanent bans are only mirrored on the site in the event of blatant trolling. Chat bans follow a similar process as outlined below, with the exception that they are handled by Chat staff rather than the Disciplinary Team. There is cross-over between chat-staff and Disciplinary, but the bans are usually separately dealt with.

The Appeals Process:

An appeal is defined as a request to commute and/or reverse a disciplinary decision.

Users may appeal by reaching out to any member of the Disciplinary Team in any way they feel comfortable doing so, provided that a record of their appeal can be provided. (Voice conversations cannot be accepted as an appeal.) This can be through Site PM, discord, email, etc.

Users may also appeal by appearing in #site17 on our IRC network and requesting to speak with any member of the Disciplinary Team.

A user may request clarification of the reasons for the ban before appealing, and staff will accommodate any request for clarification by outlining the reason for the ban and providing a link to the 05command record of their ban.

The user may then outline their reasoning as to why they believe the Disciplinary decision should be commuted (ie. having a ban length shortened) or reversed (ie. having a ban removed). Any appellant will be granted a reasonable length of time within which to make their appeal. Once the appeal has been made, it will be presented to the entirety of the Disciplinary Team for discussion. This might take anywhere from a few minutes to a day or so, depending on members’ real-life availability.

In the case of an appeal for a site ban, the appeal will then be added to the user's 05command record and the Disciplinary Team will voice their opinions upon the appeal by voting to accept, to deny, or to commute. Any decision requires a minimum of three votes in support in order to be confirmed. (ie. 3 votes for denying, 3 for a shortened ban, etc.) Once made, the decision stands unless overruled by a supermajority (60%, rounded to the nearest integer) of the Disciplinary Team or by Administrator's fiat.

Appeals of chat bans, on the other hand, are discussed amongst available chat staff and are decided internally.

Whenever possible, votes on appeals should include a statement declaring the reason for the vote. A statement of support for prior reasoning is acceptable.

General notes on appeals:

  • Take the appeals process seriously. Rule 0 still applies, especially in appeals.
  • Abusive language will not be tolerated in appeals and will be grounds for immediate rejection of the appeal.
  • Consider your words before you say them. Do they adequately respond to the reason for the initial ban? Stay on-topic.
  • Once a decision on appeal is made, it is done. Continuing to hassle additional staffers is generally frowned upon. We will know if you go to multiple staff to ask.
  • Take the time to read through the 05 thread(s) that led up to the ban. If you don’t understand what something means, ask for clarification. We don’t want to hide information, we want everything to be as clear as possible.

VI. Other things that can get you in trouble

These include, but are not limited to:

  • Behavior that is indistinguishable from trolling: When it comes to trolling, staff take an "if it looks like a duck" approach. The end result is the same and we don't want that kind of behavior here.
  • Raiding another site: Do not use the wiki or related platforms to organize disruption of the normal operation of another site. If someone else is doing this, don't take part in it.
  • Stirring up shit: This means "a pattern of constantly toeing the line of unacceptable behavior". Negative patterns of behavior that are established and determined to be a detriment to the site or community are never tolerated for long.
  • Art Plagiarism: Any art you post to the wiki must be compatible with the site's CC BY-SA license (for example: a CC-BY or a Public Domain license). If you trace, recreate, or heavily reference an image, it must also be compatible with this license and you must cite it. Failure to cite your sources in the above cases is grounds for disciplinary action equivalent to literary plagiarism. In addition, artworks which are made by using references non compatible with CC-BY-SA must be modified past recognition from said references.
  • Vandalism: Making malicious edits to pages without proper authorization will result in a ban, the length of which will be decided by the Disciplinary team. Unauthorized edits without malicious intent will result in a revocation of membership, with ban implementation at the discretion of the Disciplinary team.

All rules are subject to interpretation by staff. Everything on this page is subject to change after review by Staff.

See Also

The SCP Foundation Wiki is licensed under CC BY-SA 3.0. All rules regarding image use are dependent upon this fact.

For information on general licensing of the SCP Foundation Wiki, please read the Licensing Guide.

For image/media sites that have been approved for use, see the Whitelist under CC-Compliant Images/Media. If attempting to use media from a site that has not been approved for use yet, please contact a member of Licensing.

The terms of the Creative Commons Attribution-ShareAlike 3.0 Unported (CC BY-SA 3.0) license are thus:

  • Any use of media licensed under CC BY-SA 3.0 must include attribution to the original source of the media. (BY: "Attribution")
  • Any material using media licensed under CC BY-SA 3.0 must also be licensed under the same license, or another compatible license. (SA: "Share-Alike")
  • No other restrictions may be placed on media licensed under CC BY-SA 3.0.

These are the only terms that are applicable to images on the SCP Foundation Wiki. Only images verifiably under licenses that include some or all of these terms and no more, or which are verifiably in the public domain, are permissible for use.

Non-Compliant Licenses/Media (things you can't use)

Copyrighted (All Rights Reserved) images: The terms of their use is reserved to the original author of the image, placing many impermissible restrictions.

Images that require purchase to obtain their license (such as paid stock images): The terms of their use are so inhibiting as to require actual money to use it. As a note, manipulating an image to remove any watermarks or other features that would indicate it has been stolen is illegal and will not be tolerated. Remember: Just because it's on Google doesn't mean you can use it.

Images that you cannot find the license for: These cannot be verified to be cc-compliant or not, and thus are not permissible. If you cannot find the license of an image, do not use it.

Images licensed under the NC "NonCommercial" Creative Commons license: This places a restriction on allowing licensed media to be used for commercial purposes. The SCP Foundation Wiki is inherently commercial, by virtue of it not being a restriction placed by CC BY-SA 3.0. Thus, NC-licensed images are not allowed.

Images licensed under the ND "NoDerivs" Creative Commons license: This restricts adaptations of the licensed media. The SCP Foundation Wiki inherently allows adaptations of its content to be made, as there is no restriction in CC BY-SA 3.0 stating otherwise. Thus, ND-licensed images are not allowed.

Licenses that are not Creative Commons but still carry restrictions of their own: Even if these licenses allow commercial use, if they contain restrictions that are not present in CC BY-SA 3.0, they are non-compliant. Keep in mind, there may be sites that claim on the surface to be licensed under a Creative Commons license, but in fact have restrictions not present in the original license as well. Always read the fine print.

Images of excessive nudity/pornography and/or excessive gore are not allowed. What counts as excessive nudity/pornography and/or excessive gore will be decided on a case-by-case basis by SCP Foundation Wiki Staff.

Images that are AI generated are not allowed, unless otherwise stated.

Rule of thumb: When in doubt, ask the licensing team.

CC-Compliant Images/Media (things you can use)

Simply put, the only images allowed for use on the wiki are those licensed under these licenses:

  • Creative Commons Attribution (CC BY) 2.0 and 3.0.
  • Creative Commons Attribution Share-Alike (CC BY-SA) 2.0 and 3.0.
  • Public Domain
  • Creative Commons Zero (CC0) 1.0
  • Images you took yourself See “Personal Images” below for more information

Note that certain International Branches of the SCP Foundation Wiki do not allow the use of CC 4.0 images due to technical differences, so keep this in mind regarding translations of your article(s). However, the -EN branch does currently allow uses of 4.0 images as due to low likelihood of complaint from the licensors.

You may use images under these licenses singularly and/or combined together via photo-manipulation software (as long as the software itself is cc-compliant). The final license of an image combining two differently licensed images would be the license among the two images that's the most restrictive.

Note that this applies to media besides images as well, including films, audio, etc.

Personal Images

You are allowed to use images you, the author/artist, took yourself. All that you need to do is also state that you release your image in a license that is compatible with CC BY-SA 3.0. Before you do that, however, please read the entirety of this section.

The reason you can do this is because when you take a photo, you automatically own the copyright to said photo. This means that, as you own this photo, you can do whatever you want with it - even use it in an SCP article.

As you may have noticed, however, we don’t allow the usage of copyrighted images on the wiki. “How does this work?” you may ask. The reason why YOU, the image owner, can do so, is because you own the rights to that specific image, and can choose to release that image under a license compatible with CC BY-SA 3.0.

WARNING: When you release an image under Creative Commons, you cannot revoke that license. Please do not release an image unless you are absolutely, 100% sure you are okay with it. To understand what it means for something to be released under CC BY-SA 3.0, please see the Licensing Guide.

If you’re unsure as to what each license entails but want to use that image in an article, we encourage you to release your image under CC BY-SA 3.0, which is the site’s license. If you have any other questions, please contact a member of the Licensing Team.


Throughout the internet, there are scores of websites that claim to host thousands of public domain images; however, an examination of these websites reveals that they obtain their content via scraping off other, more reputable websites. Additionally, these image sites may host further problems. MaxPixel, for example, has the dubious honor of users downloading malware when downloading images. Pikist reverses the images it finds and claims them as its own. These scraper websites take the template of sites like Pixabay and Pexels, all without attributing those who took the images.

The SCP Wiki is well aware that the nature of the public domain means that attributing image creators is not necessary. However, the wiki requires all users to attribute all media they incorporate into their articles, regardless of origin. As such, the wiki has implemented a whitelist of approved sites to obtain images from.

Please note, however, that some of these sites host both images compatible with CC BY-SA 3.0 as well as those that are not. Make sure the image you are taking is under a usable license. If you're not sure, please message a member of Licensing.

Attribution (you have to do this)

When attributing images used in your article, you must include the License Box at the bottom of the article with the attribution information. If it's an SCP, place it under the article's Wikiwalk footer. See the Licensing Master List for instructions on how to include it. You may also include attribution in the discussion page of your article, preferably in the form of an author post, but the License Box in the article itself is mandatory. The attribution format is as follows:

> **Filename:**
> **Name:** (if different from filename)
> **Author:**
> **License:**
> **Source Link:**
> **Derivative of:** (If applicable)
> **Additional Notes:** (Optional)

Images Sub-Team Procedure

If an image is found to disobey the Image Policy, the image may be taken down immediately or the author of the article may be messaged to produce replacement images within a week's time, after which the image will also be removed. Generally, if an author is inactive (that is, their articles are under staff purview), images will be immediately removed, whereas active authors will be notified of the non-compliant image(s) prior to removal.

If an image is requested to be taken down by the original image author, it will be done so immediately without question.

Images removed for non-compliance cannot be reinstated unless there is proof it is cc-compliant. Repeated reinstating of non-compliant images and/or sassing members of staff for performing licensing duties may result in disciplinary action.

Articles under staff purview may have their images replaced without consultation of the author. If the author wants to take down any staff-sanctioned replacements, they are entirely within their right to do so. Similarly, authors may revert staff image-replacements if they have evidence they produced the image/the image was cc-compliant.


Please visit #site34 on IRC if you wish to discuss any questions regarding Images Policy not explained in this guide with a member of the Licensing Team. Alternatively, you may email moc.liamg|gnisneciLPCS#moc.liamg|gnisneciLPCS for similar queries.

Please note: if you are not a staff member, do not take licensing issues for offsite work into your own hands.
If you direct the creator or operator of an incorrectly licensed fan work to this page or suggest that they talk to staff, that is fine. Similarly, if you alert the Licensing Team to the issue so that they can deal with it, that is also fine. It is not fine to make threats about potential takedowns or represent yourself as an authority on the wiki's licensing.
The wiki has a Licensing Team for a reason. Let us help you.

For information regarding image licensing for use in articles, please see the Image Use Policy. If you've read the guide below but still have questions, please contact the Licensing Team directly at moc.liamg|gnisneciLPCS#moc.liamg|gnisneciLPCS.

In order for your derivative work to be kosher, you need to do two things:

1. Attribute the works that you're using to the wiki and to the specific author, if possible. For example:

682's Lovely Tea Party is based on "SCP-682" by "Dr Gears":

2. Add the Creative Commons Attribution-ShareAlike 3.0 license (or CC-BY-SA for short) to the derived work. Doing this will release it under the CC-BY-SA license. Specific release statements may be found under the "For Specific Creator Types" tab.

Releasing it under the CC-BY-SA license means that people will be able to copy your work wholesale, and even sell it, provided that they properly attribute you and release their work under the same license.

Do not sell anything related to SCP-173's former image, Izumi Kato's Untitled 2004. The image is not released under Creative Commons. Commercial use of this property may result in serious legal action against the seller.

See the final tab "A Word on SCP-173" for more information.

Hopefully that wasn't overly intimidating or confusing. If you have any questions or concerns, feel free to contact our Licensing Team!

The SCP Foundation community is dedicated to providing a harassment-free experience for everyone, regardless of gender, gender identity and expression, sexual orientation, disability, physical appearance, race, religion, or other personal traits.

We do not tolerate harassment of participants in any form.

This code of conduct applies to all SCP Foundation community spaces, including the SCP Foundation wiki, #site19, #site17, The Official Discord and private messages to other community members.

This code of conduct may also apply to behavior in areas associated with the SCP Foundation Community; harassing behavior in unofficial areas such as Twitter, Facebook, or Discord may result in consequences in official community space.

Anyone who violates this code of conduct may be sanctioned or expelled from these spaces at the discretion of the Anti-Harassment Team.

What Is Harassment?

Harassment includes, but is not limited to:

  • Negative or unwanted interactions with (or comments towards) a person related to gender, gender identity, sexual orientation, race, physical or mental attributes, etc.
  • Sexual images or behaviors in inappropriate places and contexts, especially when directed towards other users.
    • For instance, sexual imagery is permitted in #site19 when tagged "NSFW". However, a sexual image or comment sent to a person who hasn't asked for it is usually harassment.
  • Unwelcome sexual attention, including sending users sexual images, pressuring sexual discussion or interaction, or repeated unwanted flirting.
  • Threats of violence or encouragement of any form of self-harm toward any individual.
  • Deliberate intimidation.
  • Following users to other sites or stalking them online.
  • Repeated inappropriate social contact, such as requesting/assuming inappropriate levels of intimacy with others.
  • Repeated one-on-one communication after being asked to stop.
  • Publication of private communication for the express purpose of humiliating/shaming/harming another user, including 'outing' aspects of another person's identity without their consent.
  • Frivolous/false accusations with the explicit intention to get someone else banned from the site.
  • It is the responsibility of adults to ensure avoidance of discussing inappropriate subject matter with or amongst minors; interpretation will be upon case by case basis of the AH team.
  • Encouraging any of the above behavior.

In addition, the Anti-Harassment Team's purview extends to the below behavior(s):

  • Long-term patterns of consistently manipulative or abusive interpersonal behavior within the SCP Foundation Community
  • Egregious offenses may be pursued without permission of the targeted party at staff discretion.

What Isn't Harassment?

The Anti-Harassment Team deals only with personal harassment-based offenses. Other offenses are under the purview of the site's Disciplinary Team (for the site) or chat operators (for IRC chat).

If you're unsure, feel free to ask a member of the Anti-Harassment Team or whichever staff member you feel comfortable with.

Rules Violations

It is entirely possible to break the rules without harassing anyone. If someone is being an asshole, acting unnecessarily aggressive, or expressing bigoted, non-targeted opinions, it does not necessarily mean they're harassing someone.

If you feel that any rule-breaking behavior took place which targeted either you or another user for the purpose of causing harm, then you should report it to the Anti-Harassment Team.

Other Interactions

These interactions are not rules violations or harassment by themselves. This is not a complete list.

  • Critique of a user's SCP Foundation work, unless the critique is being used to further other harassment.
  • Challenging or questioning someone's beliefs or behavior.
  • Basic, public interactions with an ex-friend or a disliked user.
  • Personal fights between friends, even if the fight ends the friendship.


If you are being harassed by a member of the SCP Foundation community, notice that someone else is being harassed, or have any other concerns, please contact the Anti-Harassment Team by sending a private message on Wikidot, IRC, or Discord to any of the active members of the Anti-Harassment Team listed at the bottom of this page.

If the person who is harassing you is on the team, they will not be allowed to participate in handling your incident.

We will respond to reports as promptly as we can.

If possible, please give a record of the behavior in question. This may include linking to comments, screenshots of comments, chat logs, or copies of private messages. This will help ensure action is taken.

We would also like to know what you believe should be done. While we cannot promise that we will do as you ask, we do take the wishes of the victim into account when we take action.

If you're concerned about the status of your case, please feel free to contact the person who took your report. Sometimes these cases take time to investigate, but there's no harm in asking for an update. Similarly, if you have further information you believe is relevant, please submit it to the person to whom you initially sent the report, to avoid confusion.

If you believe that your case is not being taken seriously by the person taking your report, or you have any concern that the Anti-Harassment Team is not getting the full story from that person, please contact DrEverettMannDrEverettMann, who will ensure that it is seen.

This code of conduct applies to the SCP Foundation community, but if you are being harassed by a member of the site elsewhere, we still want to know about it.

We reserve the right to reject any report that appears to be an attempt to abuse the harassment system for personal slights, revenge, pettiness, or to silence legitimate criticism.

We respect confidentiality for the purpose of protecting victims of abuse. At our discretion, we may publicly name a person about whom we’ve received harassment complaints, though usually only if punishment is deemed necessary. We will not name harassment victims without their affirmative consent.

We will not pass on confidential details from user reports to the Disciplinary Team or other parties unless the person making the report specifically requests it. If you believe a user has also committed a disciplinary offense, you should report it to that team separately. Although there is overlap between the two teams, we try to the greatest extent possible to protect the confidentiality of users involved in harassment cases.

We will never pass on a user's age to the Disciplinary Team (or any other parties, staff or not). If a report indicates that a user is underage, the Anti-Harassment Team will not take action that results in an underage ban. We would prefer that users feel safe making reports to AHT, even if it means an underage user may remain on the site.

Anonymous Reporting:

  • If you feel uncomfortable reporting non-anonymously, you can enter #site17 as a guest or join the Official Discord and request to make a report to a member of anti-harassment anonymously.
  • You can also report anonymously with a throwaway account to SCPAntiHarassmentSCPAntiHarassment, a shared account of the SCP Anti Harassment team for the purposes of receiving anonymous reports.


Participants asked to stop harassing behavior are expected to comply immediately.

If a participant engages in harassing behavior, the Anti-Harassment Team may take any action they deem appropriate, up to and including site and chat bans.

If a community member has been banned for harassment, they may only appeal their ban to the Anti-Harassment Team.

The Anti-Harassment Team will notify the Disciplinary Team upon receiving, investigating, and resolving a case. The following information will be available to the Disciplinary Team:

  • Date when the incident occurred.
  • The number of parties involved in the incident.
  • The nature of the incident. (e.g. sexual harassment, racially motivated harassment, etc.)
  • The resolution as a summary, with any participants found to have been engaging in harassing behavior identified.

Content Posting by Banned Users

Users currently banned from the site may not submit new articles or other works to the site in any way.

Users banned for harassment concerns may not request content edits to their articles or submit any new content to the site in any way. Users banned for disciplinary matters may request content edits to existing work so long as proposed edits are not intentionally provocative, rule-breaking, or be so universal as to constitute a de facto new piece. Proposed edits will be considered on a case-by-case basis with no guarantees of acceptance.

Attempts to circumvent this policy will be seen as justification to deny any future edit requests.

All banned users may request deletion of their existing work or works, and staff will comply as soon as they are reasonably able to.

Anti-Harassment Team Staff

Team Captain


Team Members

thedeadlymoosethedeadlymoose (Reserve)

Inactive Members

General Account For Receiving Reports (Not a staff member)


The passcode for being accepted to the wiki is located on the Join the Site page. Chat Staff will not help you find it.

<+Reverend> IRC is just multiplayer notepad.

If you're already a well-versed IRC user, then point the client of your choice to (Ports 6660-6669 are available, as well as 6697 for SSL with SASL enabled) and join us in #site19 (you will need to register and identify before joining). Please proceed to the 'Rules and Guidelines' tab.

If none of that makes a bit of sense to you, please read these basics in their entirety before attempting to chat, because it probably will not work otherwise.

IRC (Internet Relay Chat) allows for discussions across multiple channels, which are prefixed with a #. For example, #football, #cats, and #techsupport would be topical channels people might congregate in. You can also have private, 1-on-1 conversations with people, and even create your own channels to discuss whatever you'd like.

On the "Click Here To Chat" tab, you'll see something that looks like this:


If you have never registered a SkipIRC account (which is entirely separate from Wikidot accounts), you will be required to do so before you can join our main channel. This is easy. Go ahead and hit Connect, you'll see something like this:


I've highlighted some relevant areas.

1.) Status Bar. All channels and private messages will show up here, and there are options and the leave/quit button on the right-hand side. The "SkipIRC" link is clickable and shows server information and important notices.
2.) Options. Customize the experience, add notifications, lots of little things like that.
3.) Help. This is specifically for help using the Lounge client.
4.) Mentions List. Click this for a time-ordered list of messages that included your nickname.
5.) Channel Options. This has different options depending on your abilities in the channel, and a different set of options if you're on the SkipIRC window.
6.) User List. Click this to pop out a new menu with the list of users in the channel. Some users have a prefix in front of them, they indicate a user's rank in the channel. They are ~ (owner), & (admin), @ (op), % (half-op), and + (voice). Different channels use these ranks differently. In #site19 and #site17, all users with a rank except + are chat staff (or bots that assist in performing channel duties). Users with the rank of + in #site17 are not staff, but are trusted non-staff users that can reliably give good information on basic questions.
7.) File upload. You can attach small files to share with the channels.
8.) Input box. This is where you type your messages, as well as commands like /register and /identify.
9.) Chat window. The screenshot above shows what a channel will normally look like on joining, showing the topic, then a list of users.
10.) Channel Bar. This will show the current channel as well as the topic.


We make use of three primary channels here. Most channels require registration; for more information, see that tab.

  • #site19 - For general discussion.
  • #site17 - For getting help from staff. This channel does not require registration.
  • #thecritters - For giving and receiving critique on drafts and ideas.
  • #stormofbrains - Joint brainstorming channel with discord for the development of ideas and concepts.

There are also official channels for staff teams:

  • #site11 - Technical Staff
  • #site34 - Licensing Team
  • #site77 - Maintenance and Ancillary Staff Team (MAST)
  • #site81 - Community Outreach
  • #workshop - Staff and community-led seminars and workshops.

To join a new channel, it's as simple as /join [channel] (this can be entered in any chat window). E.g., /join #thecritters will take you to #thecritters. (This can also be shortened to /j #thecritters. You can leave a channel with /part #channel in any window, or /part from the window of the channel you want to part.

You can double-click a name in the user list to begin a private message conversation with that person, and all your channels and conversations are available in the status bar.

If you have more questions, please feel free to ask chat operators for assistance.

Remember, to join chat, you must have read and understood the guide!

If you are having issues connecting, please go to the staff chat client over here.

This policy is enforced by staff, at staff discretion. Don't try to enforce this policy yourself. You can report violations in #site17 or through a PM to an active moderator or administrator (listed on Meet The Staff).


You must follow these rules when critiquing an author's work. See Site Rules for more.

  1. Critique the work, not the author. Do not make personal attacks on the author. Stick to criticizing their writing.
    • As an example, you can tell the author, "This needs work. The main idea's fine except for the X, but addenda are complete crap." Don't say, "You're a terrible writer. Why did you post this?"
    • Feel free to suggest that the author consult resources like our guides and essays, workshop their work (in the sandbox, the chat, or the forums), do more background research, or spend more time reading the site. But don't be a jerk about it.
  2. Your posts must contain some kind of content. Only saying "Meh" does not count as content, because it doesn't tell the author or other readers any information at all. An emoticon, an insulting macro, or "lol" is not content — it's spam.
    • Don't tell an author "The problems with this article should be obvious". If they were obvious to the author, they wouldn't have made them, and a post like that contains no content except obliquely insulting the author.

In short: Be helpful, civil, and open-minded.


Guidelines on Giving Critique:

  1. Criticism should be helpful in some way. Good critique suggests what the author did wrong and how to improve, or what they've done right that they should continue doing.
    • Try to give the author an idea of where to take their next draft, or what might make their current article better.
  2. Be as harsh as you need to be. Sugarcoating your criticism may give the author the impression that their draft is already great, even if it's not.
    • "Harsh" is not the same as "mean", and "mean" is not the same as "helpful". The SCP Wiki is a creative writing community — we want to encourage each other to keep writing and to improve our writing skills. Being mean or rude in your critique only discourages the author from working to be better.
  3. Forum critique should be relatively in-depth. Forum threads are made for in-progress drafts. You should make sure your critique is in-depth enough for the author to make substantial changes to their article (if necessary).
    • This is because if you respond to a post on the forums, other people (including staff) may bump that article down their priority list when responding to drafts. So if your response is just "I like it", then that author may never get in-depth critique from someone else!
    • Try to make sure you give enough criticism that an author can tell the quality of their entire draft.
  4. Critique on posted articles can be short. Articles posted to the wiki should be finished drafts, so comments posted on them do not need to be in depth — as long as they contain some kind of content.
    • Examples: You can say "I agree" (in response to another writer), or post a short but meaningful joke (so long as it's not spam or content-free). If you're not sure if you're being too brief, then post something more in-depth.
    • You aren't required to comment at all. You also don't have to explain your vote on an article.
  5. Don't dog-pile. If an article already has several significant posts about its flaws, you don't need to jump in and say you also think it's terrible. Post if you have something new to say.
  6. Keep an open mind. Try to respect stylistic choices. Maybe you personally don't like humorous mainlist articles, unusual Object Classes, or author avatars, but there's no rule about what sorts of articles other authors can try. We want to encourage people being ambitious.
  7. Remember, writing is subjective and critique is always a reflection of subjective thoughts and opinions.

If you have any questions or comments about this policy, please leave a comment in the discussion thread, or message a staff member. Thank you.

In order to maintain our standards of quality, pages found to be substandard by the community through the voting system (e.g. the Rating Box) are removed by Staff. There are exceptions for submissions that are found to be in violation of site policy. No matter the reason for deletion, staff-handled deletions are always recorded in the Announcements forum in the most recent Deletions thread, with reasons clearly given.

Grace Period

Pages are typically afforded a grace period of 24 hours after the posting of a deletion vote, during which time they are not eligible for removal from the site, regardless of rating. If a page is one hour or one year old, it doesn't matter. Everything gets a 24-hour period.

Standard Process

If a page’s rating falls to -10 or lower, that page becomes eligible for deletion. A member of Senior Staff (Operational Staff or higher) will make a post in its discussion thread, titled Staff Post, suggesting deletion. This post will have a timer on it, noting how long the deletion vote has been in place. When a page reaches three Staff votes for deletion and the deletion timer has passed 24 hours, it is removed from the site. If a page's rating falls to -20, the timer is suspended and it becomes eligible for immediate deletion provided it has three Staff votes for deletion.

If a page’s rating rises above -10, all Staff votes for deletion prior to this are voided. Should it fall again, voting for deletion must begin anew.

If an author requests a stay of deletion to make edits or rewrite a page, these may be granted. Consideration of these requests is on a case-by-case basis, as oftentimes, the best thing is to start again from a clean slate. Supplementary pages will be automatically deleted when their parent page is. Authors may repost supplements as standalone works to be judged separately as they see fit.

Reasons for Summary Deletion

There are instances when Staff will waive the standard deletions process and delete the article (with two other staff members needed as a witness). These situations are:

  • Articles with malicious intent such as, but not limited to: links to viruses, sexually explicit material, spam, advertising, trolling, and illegal content.
  • Pages that are physically harmful towards anyone who has any form of photosensitive epilepsy, or toward any user in general.
  • Pages that are clearly unfinished. (e.g. articles with blank sections or [insert text here] notes)
  • Attempts to "game" site procedure, such as re-posting a non-rewritten article in an attempt to get around downvotes.
  • Blatantly plagiarized6 material.
  • An article posted outside of the current range7. Authors may repost their articles within the acceptable range as they see fit.

Collaborative Posting:
All posted works must be written by the user that posts the work, unless specifically noted as being a collaboration between one or more site users that are current members of the SCP-Wiki at the time of publication. Collaborative works must indicate which site users collaborated in the creation of the article in question.

  • Surviving articles that are improperly attributed will be given a grace period of 48 hours from notification, where poster will be given the opportunity to provide correct attribution. After the expiration of that timer, articles that have not been corrected will be subject to summary deletion, regardless of vote count.
  • Failure to abide by this policy will result in disciplinary action, according to the usual escalation procedures.
  • This does not exempt articles from deletion via the standard voting process, should downvotes exceed stated thresholds.


Authors have the ability to delete their own work at any time. This is accomplished by:

  1. Clicking "Options" at the bottom of the page,
  2. Clicking "Delete",
  3. Selecting the checkbox for "Delete Completely."

Be sure to select "Delete Completely," as a failure to do this does not remove the page; it simply renames it to '/deleted:page-url'. After doing so, announce your choice to delete in the most recent Deletions thread.

If an author attempts to self-delete their work and fails to do so properly, either by blanking the page or renaming it, it will be deleted fully by Staff.

If an author should request their material be removed, and be able to prove authorship beyond a reasonable doubt, these requests are granted. Authors may also request deletion of all their work to be done by staff. This will likely require a basic explanation of why, and may not be immediate, but generally speaking the wiki staff will acquiesce to such requests.

If circumstances imply that a request for deletion is being made during a time of distress, or there is evidence of malice or spite on the part of the user, requests for self-deletion may be delayed or denied.

More Information

Staff have a more detailed and thorough version of the deletions guide which specifies exactly how these processes take place and the policies they follow. If you're interested, take a look at the Staff Deletions Guide on the administrative site.

The following policy concerns CSS themes, primarily those that are self-contained and may be imported onto other pages, but much of this policy also applies to embedded CSS on individual pages.


A CSS theme should be drafted on a sandbox page.

Once you feel the theme is ready, you may move it to the Wiki proper. Once you have recieved permission from a member of the Tech Team (#site11 on IRC, or on Discord), who will make sure that your theme is compliant with this policy, you may create a new page on the wiki in the theme: category with the theme tag.

Some older themes have been posted to the component: category. Please use the theme: category.

The theme must be compliant with the following restrictions, listed below.


In order to be allowed on the site, there are a few restrictions that your theme must abide by.


The theme must be released under the same Creative Commons license as the rest of the wiki.

What you can and can't change

You may change any of the style components of the wiki other than stuff that's specified in this policy.

You can't remove, hide, alter, or "break" any navigation elements of the wiki, or the rating module, or the Adult Content Warning.

You can't break the structure or look of the wiki beyond realistic expectations. The site should still be recognisable and readable.

You can style the translation module (.scpnet-interwiki-frame) using the Interwiki Style component. You are not allowed to alter or remove its contents.

Basic functionality

Your CSS theme must work well in the major browsers (Chromium, Firefox, Safari) and be at least functional in minor ones (IE 11 etc).

Your CSS theme must work well on mobile as well as desktop.

Setting up the theme's page

The theme's page is where the source code of your CSS theme is kept.

You must instruct users to add your theme to their page using Wikidot's [[include]] method (and set up your theme page accordingly. Here's a template.

You may not instruct users to add your theme to their page via CSS's @import method.8

You may not instruct users to use any Wikidot syntax which uses HTTP links, they must be HTTPS.

You must provide usage instructions on your theme's page. Note that this only refers to telling users what to type to get the theme to show up on their article. If your theme has any special features that an author should know how to use, these must be documented as well. You do not need to include examples of your theme's formatting — although you totally can, and definitely should!

Your theme's page must have your theme applied to it — i.e. your page must act as a preview of your theme. If you used the template linked above, this will be done for you.

The Tech Team member who's approving your theme will expect to see not only your CSS source code, but a draft of your theme's page.

Bloat code

A CSS theme cannot contain huge amounts of code that doesn't do anything. A CSS theme's source code should contain little, if anything, other than what this theme changes from Sigma-10 (the wiki's base CSS theme). Vast sections copy-pasted from Sigma are strictly not allowed.

Someone familiar with CSS should be able to look at your theme and know exactly what your intent is. At the very least, you should be able to justify why you have chosen to include any given line.

Additionally, you should try to avoid using the !important marker unless you really need it, e.g. to provide compatibility with other CSS where increasing the specificity would not suffice.


Accessibility concerns should be considered when composing a CSS theme. For example:

  • Is this theme readable for colorblind people? (e.g. it employs bad color combinations like red + green which make it difficult for colorblind users to navigate the site)
  • Does this theme hamper the ability to use screen readers? (e.g. it adds 'invisible' content which gets read by screen readers but not sighted users)
  • Are the fonts it uses legible for all users? (e.g. the body font size is too small, the font itself is difficult to read)
  • Could the theme induce a photosensitive epileptic seizure? (e.g. it has rapidly flashing colors or alternating patterns) If so, these elements must be removed.

and so on. Best practices and recommendations to address all of these potential issues are easily available with a cursory Google search.


Hotlinking is the practice of linking to files on another site, and is both incredibly bad practice and against site rules. It is incredibly bad manners to force someone's site to load images for your theme, and also introduces a degree of unreliability to your theme — what if that site disappears?

To prevent hotlinking, all images, fonts and miscellaneous files used in a CSS theme must be files uploaded to the theme's page rather than linked from elsewhere on the internet.

However, you are permitted to use certain sites that explicitly encourage hotlinking for serving files to users. Notable examples include Google Fonts and Lorem Picsum. If in doubt, play it safe and ask the Tech Team.

Additionally, CSS may not be linked from sandbox pages or anywhere that isn't the main site (outside of workbenches). You must use a theme: page on the wiki for CSS themes.


Your CSS theme must be completely functional on the HTTPS version of the site ( This means any internal @imports or url(…) references must refer to HTTPS URLs. For Wikidot, this means that the link takes the form

Note that HTTPS wdfiles links work even on sandboxes without general HTTPS support.


Before being posted, your theme must be approved by a member of the Tech Team. They will take a look at your theme and ascertain whether or not it is compliant with this policy.

You can find the Tech Team in #site11 on IRC, on Discord or via Wikidot PM.

Only Operational Staff and up can approve a CSS theme. The Technical Team Captains get final say in any approvals. Members of the Technical Team must get themes they created approved by another Technical Team member.

An approval from the Tech Team comes with the expectation that your theme will be posted in the next few days at the latest and with only minimal changes; if you are posting a theme long after getting approval or if you've made major changes, please re-seek approval.

Be sure to give the Tech Team plenty of time (i.e. a couple of days) to look over your theme.

Deletion policy for CSS themes

CSS themes are treated like normal pages in that other users are not permitted to make major changes to your work. Small mistakes are considered equivalent to spelling and grammar errors and may be corrected by any well-meaning user.

CSS themes are affected by the regular deletion policy, and are eligible for deletion once they fall under -10 votes.

Remediating non-compliant themes

If your theme doesn't function in the major browsers (Chromium, Firefox, Safari, mobile, IE11) in a way that completely breaks navigation, function, or accessibility, it needs to be removed (or at bare minimum, removed from include blocks) from the site, then fixed, in that order. Our first priority is compatibility, function, and accessibility.

SCP Wiki Donations Policy

The purpose of this policy is two-fold:

First, SCP Wiki Staff recognizes that there are charitable causes which serve positive moral purposes, and it is the right of our members to either further these causes directly or by raising awareness about the charity's mission within reason.

Second, SCP Wiki Staff recognizes that those who participate the SCP Wiki have the right to promote themselves and their work as an artist, author, or other contributor within reason.

This policy is intended to reflect these values.

It is incumbent upon any person advertising a donation link to vet the cause being promoted as well as the charity/organization through which they promote acting. SCP Wiki Staff takes no responsibility for the actions of any person or organization who accepts your money and fails to deliver upon any promise, either explicit or implied. We have no means and no obligation to compel recompense. SCP Wiki Staff further reserves the right to manage any donation links as is deemed necessary to protect the spirit of this policy, including measures not covered by the text on this page.

Violations of the letter of this policy are to be judged in context and, absent other compelling information, are to be treated on a "Warn and Correct" basis.

Abuse or breach of the spirit of this policy for any purpose may result in disciplinary actions which range in severity from a temporary suspension of donation linking privileges, to a permanent ban from the SCP Wiki.

Charitable Links Policy:

Links to charitable organizations may be added to your own "standard page". For the context of this policy, a "standard page" is defined as an SCP, GOI Format, Tale, or other SCP variant such as a -J. These links may additionally be collected in the author post within the discussion/comments. When amending your own standard page to include a charitable link, you are permitted to make a single announcement in the comments/discussion indicating the change, but that announcement is not to include the link itself.

Links posted to standard pages may be disguised within the context of the article, but should be identified as either a 'plain link' or by a short description if appearing elsewhere.

Links to charitable organizations may also be added to your own art, author, or project page. For the context of this policy, a "project page" is defined as an ongoing non-standard project such as an SCP webcomic, art gallery, podcast page, or game. For further clarification on the use of external site links, please review the current Tech Policy. When amending your own art, author, or project page with a charitable link, you are permitted to make a single announcement in the comments/discussion indicating the change, but that announcement is not to include the link itself.

Links posted to art, author, or project pages are required to be either 'plain links' such that their destination could not be confused, or must include a description as to the nature of the link.

Example of a 'plain link':

Example of link with description:

If you would like to support EXAMPLE-CHARITY you can visit them at [ their homepage] to donate.

Personal Links Policy:

You are permitted to advertise SFW (Safe For Work) links to places such as your personal Patreon, Ko-Fi, or other similar services in order to allow for donations or 'tips'.

Personal Links may be included in the 'information module' of an article, may be posted in the 'discussion' section of an article, and may be provided on an Author page. You may also link to a personal website or landing page, such as a, which contains collections of your personal links provided this landing page is Safe-For-Work. This Policy makes no distinction about the content which is then linked from this landing page, which may ultimately be NSFW in nature.

If you provide a personal link to a platform which charges money, you are required to be clear about when a person may be charged; as an example, Patreon has the option to pay creators either monthly or only upon the publication of material and a failure to clarify may cause undue financial problems for members.

Additionally, many social media sites and payment service options will expose a degree of personal information. Pages or posts which include Personal Links are required to contain the following disclaimer:

> Payment services may reveal information such as your real name, email address, and other personal information when you donate.

If you advertise the promise of content (such as via Patreon membership tier) you must deliver on your promised content to the best of your ability, once paid. Failure to do so may result in staff action in accordance with the spirit of this policy. It is your obligation to inform any of your financial contributors if you are experiencing delays in delivering promised content, and failure to do so may be interpreted as evidence of an attempt to scam.

Should you pay someone via a donation link, SCP Wiki Staff takes no responsibility for a content creator's failure to deliver, and has no means or obligation to recompense you.

In posting a personal donation link you agree that you are doing nothing illegal in either donating, accepting donations, selling content, or purchasing content and that you will adhere to the terms of service of any donations site used.

You are required to follow the license when making any derivative works of SCP Wiki content and also ensure that any content you intend to make money from is allowed to be used commercially. Errors in licensing could result in legal liability for some or all parties involved; The SCP Wiki Licensing Team is a resource available to you if you have questions.

If you observe any suspicious donation links or think something questionable may be going on, we would urge you to report this activity immediately in either #site17 IRC Chat, The Discord, or by contacting a member of the Disciplinary Team via private message.

Prohibited Actions:

Breach of any of the following is likely to result in immediate disciplinary action.

  • Under no circumstances may SCP Wiki Staff accept any compensation for the performance of staff duties. Any attempts to bribe staff into performing duties also constitutes a violation of this policy.
  • Under no circumstances may you attempt to buy or sell votes on the site. This includes the promise that an article would reach a certain threshold of performance.
  • Under no circumstances may you advertise donations for or the sale of content which breaks the site rules.
  • Under no circumstances may you advertise the sale of critique services anywhere on the SCP Wiki. Note that this does not prohibit critique services offered by off-site venues such as Patreon.
  • Under no circumstances may you advertise donations for or the sale of co-authorship or "vanity publishing". Articles found to have been published in such a way are subject to summary deletion, and may also include action against the donator/purchaser.
  • You may not excessively advertise content you produce as a result of donations, including overly bothering people about reading and voting on the work. A reasonable degree of advertisement is allowable as is expected with any user.
  • You may not advertise "partial donations", such as a claim that a portion of a donation will also be forwarded on to another cause or organization.
  • You may not create or participate in donation-incentivized competitions, such as offering a reward for the "highest rated tale about your author avatar". Anyone wishing to organize an unofficial contest should speak with the Community Outreach Team for approval and assistance.

Clarifications of this policy are to be directed to the Disciplinary Team

Updated 2022-08-03 by ManyMeatsManyMeats

Standard Rewrite Procedure

Step 1: Find Something to Rewrite

Most articles eligible for rewrites are rated below -10. When this happens, the article will be eligible for deletion and a vote will begin.

While the vote is open, people can offer to rewrite the article. If you are interested in rewriting the article, please message a member of the Rewrite Subteam.

You can also request to do a rewrite when an article is struggling, or an author asks for it specifically, but these are less common (see the frequently asked questions for more detail).

Step 2: Author Permission

Included page "component:image-block" does not exist (create it now)

You must have permission from the original author to do a rewrite. You can either post on the forum, send them a chat PM, or ask in a Wikidot PM (example in Image 1). If you can provide proof of author permission, such as a screenshot, then you may start rewriting.

If the author does not respond or denies your request, you are not allowed to rewrite the article. Don't bug them about it; they have the final say on their work.

If the author is no longer around (as is the case with a lot of older articles), then the Rewrite Subteam will make the final call for you. This doesn't mean you can ignore the rest of this step though! Always make an attempt to contact the original author.

Step 3: Message from the Rewrite Subteam, and Rewriting!

Once you've stated your intent to rewrite, a member of the rewrite subteam will contact you with info about the process for your specific case. They'll tag the article "in-rewrite", and you'll be able to get started.

After that, get to it! Work for as long as you like: there's no time limit. Try to stay true to the original author's idea and narrative intentions.

As an aside, please remember that while there is no time limit on how long you can take, there is a time limit on how long an article might last on the site. Often, if a while goes by without hearing from you or getting an update on your progress, the original page may be cleared. That's alright, though! You can still post your rewrite to a different slot. Just remember that if you've got your heart set on a specific number, you might not get to keep it.

Step 4: Team Clear! Feedback!

When you've got a finalized draft, ask a member of the Rewrite Subteam for feedback. This can be done via a wiki PM, or on chat. Once you've received the OK, you're free to post.

Of course, it's always a good idea to get as much feedback from other site members as possible, before diving into that mainsite post.

REMEMBER, the Rewrite Subteam may tell you that your article needs work or that you should get more feedback. In those cases, you are required to do what the team says before posting your rewrite.

Step 5: Post!

Once you've got the previous steps down, you can post your rewrite! If the original SCP number is still available, you're free to use that. If you want to use another, you're free to do that as well.

Remember to make a post in the discussion thread stating:
1. That the article is a rewrite
2. The original author's name

You're done! Wait for the votes and comments to come in and PM the original author to let them know the revamp has gone live.

Frequently Asked Questions!

Check here first to see if your question has been asked already. As more questions are asked, this list will grow.

Q.) Does doing a rewrite save the original article's number on the mainlist?
A.) No. If it's available, you can use the number the original author picked. Otherwise, feel free to use any of the other open slots to post your article! On a case by case basis, the rewrite subteam can elect to grant a stay of deletion to articles more than two years old if said articles are in the process of being rewritten and are below the deletion deadline. Should a stay be granted, prompt completion of the rewrite is expected from its author.

Q.) Do I receive author credit for my completed article?
A.) Yes! You will need to ask a wiki moderator to unlock the Attribution Metadata list for you so that you can add your rewrite to the page.

Q.) How much do I need to stick to the original article, in terms of concept and theme?
A.) Depends on who you talk to. You don't want to plagiarize and copy the original article exactly. You also don't want to write something so different that people don't see the original ideas anymore. Try to strike a happy medium where the concept of the original stays similar, but you play with variations on theme or background.

Q.) Who are these Rewrite Subteam members I keep hearing about?
A.) Currently, the Rewrite Subteam consists of:
SubTeam Captain: RiemannRiemann
Vice Captain: Uncle NicoliniUncle Nicolini
Team Members: stormbreathstormbreath, FlyPurgatorioFlyPurgatorio, LuxaikoLuxaiko, weizhongweizhong, AstersQuillAstersQuill, fairydoctorfairydoctor
Administrative Contacts: aismallardaismallard (Primary Contact), DexanoteDexanote, thedeadlymoosethedeadlymoose

Q.) What if the author never responds to my request?
A.) This is where it can get a little bit tricky. This is the current Rewrite Subteam protocol concerning this awkward situation:

If the article is <1 year old: No dice. If the author does not respond, assume that you cannot proceed with the rewrite.
If the article is 1-2 years old: If the article is 0 or negative, then proceed with the rewrite with Rewrite Subteam approval.
If the article is >2 years old: Go ahead with the rewrite if the article is <10 in rating. Articles just barely above this can be rewritten with Rewrite Subteam approval on a case-by-case basis. Contact a Rewrite Subteam member about this situation if you have a special circumstance.

A list of articles that fall under this category can be found here. Please note that this is not an extensive list and rewrite will still use discretion on a case-by-case basis.

Q.) It sounds like the Rewrite process only happens with articles at low ratings? What's up with that?
A.) Not so! Rewrites can be done at any rating as long as the original author gives their assent! If a rewrite happens to a higher rated article, you'll still need to unlist the original page and repost in the number slot where applicable! When you're cleared to post, simply let someone on the team know and we will unlist the article to make way for your rewrite.

Q.) Can I rewrite an -ARC article?
A.) Sure! In that case, once the rewrite gets to a high enough rating, the original will be unlisted!

Feel free to PM any of them with any additional questions you might have!

Table of Contents

The following set of policies concern page elements over which the EN SCP Wiki Technical Team has jurisdiction.

See also the CSS Policy, which describes requirements for posted themes or embedded CSS on the site. Note that all site styling is subject to modification at Technical Team discretion.


All page content (including themes, components, images, HTML, and attached files) must be hosted on the SCP Wiki. Linking to other Wikidot sites such as sandboxes, or linking to files hosted on a private website are not permitted. An exception exists for notable components (not themes) hosted on the SCP INT wiki and the Wikidot Snippets repository.

All files should have a file extension appropriate to their file type.

Files larger than 4 MiB may not be uploaded without staff approval. Generally, files should be less than 2 MiB in size.

Images specifically are subject to several restrictions:

  • Images should not exceed 800 KiB in file size, and should not have dimensions significantly larger than their appearance on screen.
    • Note that the default width for the standard image-block component is 300 px, so, for instance, an image with a width of 1200 px would be too large. Larger images may be uploaded, provided the reduced-size file is the one actually displayed.
  • Staff are permitted to shrink images that are too large as described above.
  • An exception exists for art pages: media there may be hosted off-site instead of on the wiki. The hosts currently permitted are:
  • Note that, for both art pages and regular pages, hosting files via Discord is not allowed. Such links will expire with time and become broken.
  • Additionally, large video files may be hosted on YouTube or Vimeo if they are on a channel that the author controls.

Due to a bug, uploaded SVGs may not be correctly recognized by Wikidot. See here for more information.

Font hotlinking is permitted if in compliance with the CSS Policy.

Offset Articles

The ListPages module allows presenting multiple pages under the same slot and rating module. See ListPages Magic and You for information on how this works.

If an offset-based article requires the creation of child pages, those pages must be created in the fragment: category, and they must be named according to its parent page and index. If the parent page is renamed, the fragment pages must be as well.

For instance, if a user posts a page my-story, then each of the offsets could be named fragment:my-story-1, fragment:my-story-2, etc.

All fragment pages must be listed in the page source, for instance:

[[module Rate]]

Fragment pages:

[[module ListPages category="fragment" parent="." order="created_at" limit="1" offset="@URL|0"]]

(Pages with ten or more fragments may provide ListPages code to list all the fragments instead)

Fragment pages must be parented to their host page, regardless of whether parent pages are used as a selector for the ListPages module.

The usage of redirect modules on fragment pages is forbidden.

If a page's tags on an offset-based article would present a significant spoiler for the reader, then, as a special exception pursuant to Tech approval, tags may be hidden on the first offset only by use of the Hide Tags component.

HTML and Javascript

Use of [[html]] and [[iframe]]s should be minimized to the fewest number of instances necessary. If two [[html]] blocks are able to be combined into one, or the content of an [[html]] block can be reasonably replaced with Wikidot text instead, they must be.

Javascript that is malicious, not compliant with the site license or cannot be justified to the Tech Team must be removed. Use of malicious scripting or exploitative page elements may result in disciplinary action.

Any HTML or javascript in a page may not take actions outside the context of an article (e.g. sending unsolicited emails or accepting payment), transmit information about the reader, or perform an irreversible action. Cookies and local storage are permitted if they are strictly necessary for the proper behavior of the page.

Additionally, page content may not create pop-ups or automatically open links that the user has not clicked on.

Minified HTML, CSS, or Javascript may be used, but the un-minified full source must be disclosed and publicly available. Like all other content, they must be available under the site's license (CC-BY-SA 3.0), though it may be dual-licensed with another free/open source license.

All flash content (extension .swf) is prohibited.

If you'd like to use audio in an article, do not use the flash snippet, use the HTML5 audio player.

Component Policy

All new components must be approved by a Tech Team operational staff member (or higher) prior to posting.

Components must abide by the same content policies as HTML, and be fully hosted on-site.

'More by' pages

Authors are permitted to create a page for listing other works by them, which they may use on their articles as a way of directing readers to more of their work and/or providing recommended reading.

'More by' pages must have the more-by tag and exist within the more-by: category. The page's UNIX name (i.e. the part of the URL that is preceded by the category) must be identical to the creator's username as it appears in the URL of their Wikidot user info page.

If the author changes their username, they must update the URL of their 'more by' page, if they have one, and they must also update all pages that use it to point to the new page location.

Unmodifiable Content

The following parts of a page are not considered "page content": they may not be removed and any modifications must be in line with existing conventions. For instance, users may not hide the ability to edit or rate the article as part of a format screw.

The color and appearance of these components may be modified if in compliance with the CSS Policy.

  • User module / login status
  • Search functionality
  • Page tags
  • Article metadata (for instance, the Attribution Metadata)
  • Rating module
  • Translation module
  • Side bar
  • Top bar
  • Wikiwalk navigation footer
  • Adult splash page (if relevant)
  • Page Preview component
  • License box component
  • Page information and buttons (e.g. edit, rate, history, etc.)
  • Wikidot advertisements (violation of the Terms of Service)
  • Wikidot footer
  • Wikidot license information


New pages must be created in the appropriate category:

  • Components and templates must be in the component: category.
  • Themes must be in the theme: category.
  • Fragment pages must be in the fragment: category.
    • A "fragment" is any page that is created for a single, specific regular page for the presentation of its content, and are not intended to be viewed directly.
    • Fragment pages are not subject to voting or deletion.
    • See also section "Offset Articles".
  • 'More by' pages must be in the more-by: category.
  • Art pages must be in the art: category.

All other pages must be in the main category (a.k.a. "_default:"). Use of other categories requires Tech Team approval on a case-by-case basis.

This means that your page URL may not contain colons (:), as the text before the colon will be interpreted by Wikidot as a non-default category.


Wikidot permits pages to be assigned a single parent, which appears at the top of the page with navigation links called "breadcrumbs". These are used to show that articles are related to a particular article, for instance with 001 proposals being parented to the SCP-001 hub.

Supplement pages should be parented to the main article that they relate to. Fragment pages must be parented to their host article (see section "Offset Articles"). 'More by' pages must be parented to their creator's author page, if they have one (see section 'More by' pages).

Due to Wikidot limitations, if an author wishes to parent their page to multiple articles, they should use the following code, rather than the standard parenting feature.

[[div class="pseudocrumbs"]]
[[[parent-page-url1|Title of First Parent Page]]] » Title of Child Page
[[[parent-page-url2|Title of Second Parent Page]]] » Title of Child Page

Authors may assign the parent of their page as they wish, provided it does not interfere with the technical implementation of other pages that they do not have authorization to edit.

Site staff are authorized to assign page parents to improve site navigation and accessibility.

Page Titles

All pages must have a title: it may not be blank. This is because ListPages selectors and forum pages have rendering issues if the title field is empty. A page's title may be hidden with CSS to create the appearance of not having a title.

Users can make the displayed title of their page different from the system page using the following code:

[[module CSS]]
#page-title {
    display: none;

[[div class="meta-title"]]
New Title Here

SCP Titles

Not to be confused with Page Titles, SCP titles are the text that follows its associated link on the SCP Series pages with the following format:

[[[SCP-XXXX]]] - Title of SCP

The link part ([[[SCP-XXXX]]]) represents the Page Title of the article; which should not be used to substitute the metadata title (Title of SCP).

To ensure technical and parsing compatibility, there are limitations to ensure standardization and avoid issues with site technical policy.

Titles must be primarily composed of plain text, and are reasonably accessible to screen readers. For example, "zalgo text", misusing mathematical characters as alternate "fonts", and use of the Private Use Area (PUA) would be prohibited, as well as excessive usage of emoji. However, this does not preclude the use of non-Latin characters when appropriate.

  • Example of appropriate usage of non-Basic Latin and Latin-1 Supplement Unicode characters: SCP-5040 - 血の涙 ("Tears of Blood")
  • Example of inappropriate usage: SCP-XXXX - 𝐃𝐄𝐀𝐃 𝐁𝐎𝐃𝐘 (Mathematical Bold Capital letters used for stylistic purposes rather than mathematical notation.)

Limited formatting for accurate representation of text may be permitted with Technical Team approval. For instance, use of superscript or subscript for strictly technical information (e.g. "H2O" or "21024 bytes"), or use of the "ruby text" CSS class for CJK-compatible text displays. Use of these features for "stylistic" reasons is not permitted.

In addition:

  • Use of CSS modules and/or external stylesheets to supplement titles are prohibited.
  • Use of inline formatting are restricted to the following:
    • bold (**bold**)
    • italic (//italic//)
    • underline (__underline__)
    • strikethrough (--strikethrough--)
    • teletype ({{teletype}})
    • Escaping with @@
    • color (##blue|color##)
      • Use of color syntax to render text invisible, obscure or otherwise difficult to read is prohibited.
    • [[span]] with inline CSS (no class). Only the following properties are allowed:
      • All font properties
      • All background properties (excluding use of external or encoded images)
      • padding properties
      • All border properties
      • color
      • All text-decoration properties, text-shadow, letter-spacing, word-spacing
      • box-shadow

The Tech Team reserves the right to edit titles and alter formatting if deemed too disruptive or deleterious to accessibility and legibility. Determination of violation is subject to Technical Team's discretion.

Preview Content Policy

The Preview component can be added to the top of the page to expose a hidden but query-able blurb for an article. This may be any text which accurately or usefully describes an article at a glance or in summary. However, there are limitations to ensure standardization and avoid issues with site technical policy.

Blurbs must be primarily composed of plain text, as defined in the SCP Titles section.

  • Syntax blocks (e.g. [[div]]), custom CSS (inline or through modules), and use of components are prohibited.
  • Use of inline formatting are restricted to the following:
    • bold (**bold**)
    • italic (//italic//)
    • underline (__underline__)
    • strikethrough (--strikethrough--)
    • teletype ({{teletype}})
    • Escaping with @@
    • Inline center text (= at the start of a new line.)
  • Use of the component is limited to pages in the default category.
  • Blurbs must be at least one sentence or equivalent in length.
  • Blurbs should describe, summarize, or provide a hook for the article they reference. Off-topic or inappropriate blurbs may be subject to edits at the discretion of the Curation Team.
  • Blurbs should not be disruptive, such as containing excessively many paragraphs. This is determined at staff discretion.
  • Blurbs may contain links when appropriate, e.g. to a series it's a part of, or to a sequel/prequel article.

The Tech Team reserves the right to edit blurbs as necessary if deemed too disruptive or deleterious to accessibility and legibility. Determination of violation is subject to Technical Team's discretion.

Page Tags

Tags are defined by the Tech Team for wiki organization, categorization, and navigation.

Any changes to tags should be performed by the Tech Team or MAST (or, in the case of license-based tags, the Licensing Team). Objections to tagging decisions should be relayed to the respective team for discussion; users are not permitted to revert tag changes made by staff members.

Users may suggest new tags in the appropriate stickied threads within the Proposals and Policy forum.


Wikidot provides the Redirect module, which, when added to a page, causes any browsers visiting it to instead load the destination page. This can be disabled by appending /noredirect/true to the page's URL.

Users are never permitted to add a redirect to an article that is not theirs. Additionally staff approval is needed to create a page solely to act as a redirect. All pages containing redirects must bear the redirect tag.

Redirects may not point to pages off of the main wiki, including sandboxes or other Wikidot sites. Fragment pages may not contain redirects.

If in doubt, get explicit staff approval.

ListUsers Module

The ListUsers module allows authors to call upon the username of a reader, and insert that username into an article. However, it also limits content to only be accessible to users who both have an account and are logged into it, meaning that users who are not logged in or do not have an account cannot read parts of the article.

As little content as possible should be gated behind a ListUsers module. Generally speaking, this means that the ListUsers module should only contain the specific paragraph in which the username is being mentioned. The article should not have substantial or major differences between the version that is displayed to a user who is logged-in, versus the version displayed to one who is not.

Wherever possible, the ListUsers components should be used, rather than the base Wikidot functionality. This component allows for alternative content to be displayed to a logged-out user, and should be used to present an equivalent version of the gated content that does not reference username.

Link Shorteners

Link shorteners and QR codes are not allowed on the SCP Wiki. As the character limit of a wiki page is long enough to not be a concern, neither of these is necessary. Further, as they disguise links and make the destination unclear to a user, they pose a mild security concern.


The following section refers to the Wikidot function called "Renaming", which allows users to change the url of a page they have posted. This is also sometimes colloquially known as "moving".

The Tech Team offers a minor caution against renaming, as it can leave extant links elsewhere on the internet voided when a page moves. In many instances, these links cannot be edited or are not under the control of the original author, and those links will now either link to a nonexistent page or an entirely different one. This is simply a warning to be careful about renaming, not a prohibition against it entirely.

Deleting pages is technically considered renaming due to circumstances in the Wikidot backend. This is considered an auxiliary usage and is not covered in this policy.

Renaming Pages

Users are allowed to rename pages under their control as they see fit. They may put the article in any valid slot they choose. Be sure to follow the steps below when renaming a page:

  1. Go to the bottom of the page and check the backlinks, in the + Page Options. If there are any backlinks specific to the article, write them down. (You can ignore the mainlist and Wikiwalk footer.) Be sure to do this step before renaming the article.
  2. Rename the page with the option named "Rename" in + Page Options. Do not instruct Wikidot to fix backlinks.
  3. If the article referred to its url, fix those references. Most SCP articles do this.
  4. Edit any backlinks recorded in Step 1.
  5. If there are any files on the page that were called with their full urls (rather than simply the abbreviated file name), update those to the new url.
  6. In the case of a mainlist article, edit the respective mainlist so that the title of your article is at the correct location.
  7. Leave a post in the Updates Thread of the Page Announcements forum detailing the change.

Co-Authored Pages

In the case of a co-authored page, you must consult with your coauthor(s) to make sure they are also willing to rename a page. If you have full control over the article due to your coauthor's absence, you can proceed as normal. If your coauthor is not willing to rename, do not rename the article.

If you did not post the article, and have permission from your coauthor to rename, but they are unable to do so for whatever reason, ask for staff to rename the article, in #site17, #observer-discussion or #help-desk. A moderator will then complete the above steps for you.

Renaming SCPs

Renaming SCPs carries an additional caveat: You can only rename an article into the most recently opened series. You may not rename an article into an older series. Extant articles that are renamed into older series will be reverted to their original url. If that url is no longer available, they will be given a new slot in the most recently opened series.

This means that should an article in Series 1 be deleted, you cannot rename an article you already have posted in Series 9 into that url. However, if you already have a Series 1 article, you could rename that article into a Series 9 slot, and then post a new article into that slot.

Style Resource

The SCP Style Resource is a collaborative page maintained by the Tech Team. The team may provide limited support, but all components are considered "as is".

Any added components must comply with the policies listed here, and are subject to modification or removal at staff discretion.

This is the formal policy for Translations posted on the English Language SCP Wiki - for a list of translations and instructions for posting them, go to the International Branches Hub.

What is a translation?

A translation is taking an article from another site and translating it into English to post on the SCP wiki. In cases of articles with no text (see SCP-2521 for a very well known example), this may involve no changes.

What translations are allowed?

If an author has specifically asked for a work not to be translated, you are not allowed to post a translation of that work onto this wiki. Getting permission from the author to post your translation is recommended, but not required.

If the original work is not from a recognized SCP branch (see for a full list), then you must obtain explicit author permission to post it here.

You must either be the author or the translator of the work to post it onto the SCP wiki, or be posting at the request of the author or translator and giving them full credit and control over the article.

Unlike most articles, it is not required that the original author of the article that has been translated be a member of the SCP Wiki.

Proxy posting requests by staff

If an article exists on the -INT wiki, the translator may request that SCP staff post the article onto the SCP wiki. If the translator is impossible to contact, then the original author may also make the request. This only applies if the translation can be posted here anyway.

Changes to Translations

Any site member is permitted to correct the spelling, grammar and phrasing of a translation in order to fix errors and make it more accurate to the original. In cases of disagreements, the person that posted the translation should have the final say on what the wording should be.

If minor changes are made to the original article, any site member is welcome to translate those changes and update the translation.

In the case of a full rewrite or delete of the original article, the translation will be archived (URL moved to a -arc, not archived:) or deleted, as decided by the translator and author, so that a new translation can be uploaded.

Author/translator rights

The translator always has the right to have their translation deleted from the SCP Wiki.

The author(s) and translator(s) will be treated as coauthors. The author can later request to have the translation deleted, but this will only be done if the translator agrees.

Where to post

In all cases you must post to the same unix URL as the original page. As an example, a tale from the -IT branch with the URL should be posted at, to ensure the interwiki box in the bottom left works.

While permitted in the past for articles like SCP-179, going forward this policy will prohibit the posting of translations to the SCP Wiki mainlist. If posted today, SCP-179 would need to be posted as, to match the URL of the Spanish original, This policy will not be enforced retroactively, but going forward if a translation is posted as if it were an original SCP written in English, the person posting it will be asked to decide whether to delete the translation or to rename it to match the URL and SCP designation of the original article.

Exceptions to this rule will be permitted at the discretion of site staff, to cover situations in which two original articles on two different wikis share the same unix URL, making it impossible for both to share the same unix URL when translated onto the same wiki.

Licencing, tagging and metadata

All international works must have the original author included in the licencebox as the author, unless the author is also the translator.

All international works must have the international tag and, if it is from an official branch, the language tag (like _ru for russian). Translations are tagged like any other article, so if you are not familiar with tagging just tag with international and the branch name, and a tagger from MAST will fill the rest in.

If the translator is not the author then that must be noted on the metadata page. Translators should contact a moderator for this.

Reposting a deleted translation

The same policy for reposting deleted articles applies to translations - there must be some difference between the two posts.

Translations and votes

Translations that go below -10 undergo deletion, as per a normal article. Votes on translations can take into account both the quality of the translation and the subjective assessment of its content.

Translations from EN

All translations from English to other languages should go on the proper site, and not onto this wiki. If there is not yet an Official or Developing branch, translators are welcome to post their work on the Underrepresented Language Incubator on the International Translation Archive.

Content Warning: This guide discusses a variety of adult themes.

rating: 0+x

With the implementation of the new adult content warning component, we intend to make the process and reasoning for applying these content warnings to articles clear to readers, authors and staff, by outlining the rules and requirements in this guide.

This is not intended to replace existing methods for warning about adult content, such as banners at the top of articles or the info box content warning, but to supplement them. Many types of content may warrant a content warning but would not result in the article being considered adult, including bigotry, slurs and most violence and body horror, and we encourage authors to continue adding content warnings as they deem appropriate.

Table of Contents

The Adult Content Curation Team

Adult Content Warnings are the responsibility of the Adult Content Curation Team, which is part of the Curation Team. Members of the Adult Content Curation Team are listed on the Curation Team Hub, and can be contacted via private message, via the #help-desk channel on the SCP Wiki Official Discord server, or via IRC chat #site17.

As a team, we are conscious that we are likely have personal and cultural biases affecting what we consider as adult. Since this will always be a subjective judgement, we've decided to err on the side of being too cautious and potentially tagging too much, rather than too little. If we find ourselves debating whether or not a specific article is actually adult, we'll probably just label it as adult. Ultimately, we'd rather leave the decision of whether or not to engage with potentially adult material up to our readers, and to use the content warnings to enable adult audiences to make informed decisions.

Adding and Modifying the Adult Content Warning

Authors are free to label their own work as adult, by adding the _adult tag, including the Adult Content Warning component, and adding the appropriate content warnings. We'd recommend doing this if your article contains any sexual content, since this will always be given an adult content warning. Other content warnings are more subjective and we'd recommend getting in touch with the Adult Content Curation Team if you think your article may be adult based on non-sexual content, or if you're unsure how to correctly label your work as adult.

People who read potentially adult content posted by others should get in contact with the Adult Content Curation Team to recommend that they review the article. If possible, suggest content warnings, so we know what to look for. Do not add the Adult Content Warning component or adult tag to other people's articles without permission from the Adult Content Curation Team.

It is not permitted to remove an Adult Content Warning added by a member of the Adult Content Curation Team, or to alter the default content warnings chosen by the team. If you disagree with their reasoning, you will need to get in touch to discuss removing or altering it.

Authors have much more freedom to suggest custom content warnings to supplement or expand on the default ones, although these must remain strictly informative. Custom content warnings will need to be approved by a member of the Adult Content Curation Team if they haven't already been used as a custom content warning on another article. When proposing a custom content warning, remember that content warnings on the Adult Content Warning component should be phrased consistently, and should be easily understandable and appropriately serious. Redundancy between the custom content warnings and the set of standard content warnings should be avoided, and content warnings should be kept short to make it more likely that people will actually read them.

The Adult Content Warning has a deliberately uniform appearance to ensure optimal visibility and consistency across themes. As specified in our CSS Policy, it is not permitted to alter the appearance of the Adult Content Warning. If specific themes or components cause issues with the Adult Content Warning, contact the Adult Content Curation Team or the Technical Team.

In cases of collaborative articles where multiple authors submit their own works, the Adult Content Curation Team may decide to place an Adult Content Warning over a specific section or sections, although the page would still be tagged as adult. This will only be done if the majority of works submitted do not qualify for an Adult Content Warning. In most cases, removal of adult content from a collaborative page will be a more appropriate response than placing it behind an individual content warning.

The Adult Content Warnings

While the component itself explains how to add it to articles, the various content warnings may require further explanation. The default content warnings built in to the component are:

  • Gore - Graphic depictions of blood, gore or mutilation of body parts.
  • Sexual References - Features sexual themes or language, but does not depict sexual acts.
  • Sexually Explicit - Explicit depiction of sexual acts.
  • Sexual Assault - Features non-consensual sexual acts.
  • Child Abuse - Depiction of severe mistreatment of children.
  • Self-Harm - Depiction of self-harm.
  • Suicide - Depiction of suicide.
  • Torture - Depiction of torture.

This is not a comprehensive list of all possible content that may be considered inappropriate or triggering, and so authors have the option to add custom content warnings. Custom content warnings need to be approved by the Adult Content Curation team first, to ensure that the Adult Content Warning remains purely informative.

Any of the default content warnings could be considered a valid reason to tag an article as adult, but not all articles that explore these themes are necessarily adult. The Adult Content Curation team reserves the right to add additional content warnings to this list, or to tag articles as adult for reasons not currently on this list, via an appropriate custom content warning.

Content warnings are intended to be self-explanatory, but if you're interested in exactly when and why they are applied, read on.

At least so far, adult content warnings for sexual content are the most frequently applied. The Sexual References content warning applies to articles featuring highly suggestive language, sexual themes such as pornography or sex work, or discussion of sexual acts or genitals. It is superseded by the Sexually Explicit content warning, which is applied to articles that describe sexual acts, so articles should only have one of these content warnings. The difference between these two content warnings is basically reducible to the difference between an article that discusses sex and an article that depicts sex. If the article features non-consensual sexual activity (which could be anything from groping to rape), then the article will be given the Sexual Assault content warning, which also supersedes the Sexual References content warning. It's possible for an article to get a content warning for sexual assault without being sexually explicit, since sexual assault may be discussed without being described, and so if appropriate an article can have both the Sexually Explicit and Sexual Assault content warnings.

Gore in isolation will only get an Adult Content Warning if it's particularly extreme or graphic, since written descriptions of gore and body horror are generally regarded as less severe than a visual depiction would be. However, the Gore content warning is often used in combination with other adult content warnings, and in that case the standards for applying it are less strict, since depiction of mutilation and violence may make other kinds of adult content more disturbing.

References to child abuse, suicide, self harm and torture would not result in an article being given an Adult Content Warning, but depictions may. For suicide, self harm and torture, detailed descriptions of the act would warrant an Adult Content Warning. In articles featuring children, the implication of physical or sexual abuse may warrant an Adult Content Warning, even in the absence of detailed information about the nature of the abuse.

Guide for Posting Anonymous Articles:

Step 1

Message a member of the Rewrite Team to inform them that you wish to post an article anonymously. This message should contain a link to the article you wish to post, as well as the title, desired slot, and author post. You must qualify for an author page (3 surviving works) to qualify for anonymous posting.

Step 2

The Rewrite Team will make a copy of the article and do a review to make sure that the article does not contain any rule breaking content. Please allow the team sufficient time to review the article.

Step 3

Once the article has been cleared, it will be posted by the Rewrite Team using the "The Community" account, at the anonymous author's discretion.

Please note that the Rewrite Team will maintain a list of the authors of anonymous articles. Only Rewrite members and admins have access to this list, though parts of it may be shared with the Disciplinary team in extreme circumstances.

The Rewrite Team reserves the right to deny posting an anonymous article.

If you wish to de-anonymise an article, please message a member of the Rewrite team. Submitting an anonymous article for a contest counts as your submission for that contest. Posting a regular article for a contest after an anonymous one will result in the deletion of the regular article and de-anonymisation.

rating: 0+x


What's a tag, and what are they used for?

Tags are keywords that can be found at the bottom of any page on the wiki, that will allow you to find other pages with similar elements, characters, or settings. You can use the page Tag Search 2.0 to combine multiple tags and find articles tagged (for example) euclid and humanoid, or automaton, keter, and broken-god, or you can click on a tag you see on a page to get a list of all pages tagged with that specific tag. If you're not seeing any, that means a member of the Maintenance and Ancillary Staff Team have yet to tag the article, but will do so eventually.

Due to the use of tags in staff processes, any user who incorrectly applies tags to an article will receive a tagging infraction. The user who applied the tag will receive a PM explaining their mistake, and if a user accumulates three total infractions, a C&D may be applied, and any further infractions will be met with disciplinary action.

The following actions will incur a tagging infraction.

  • Adding or removing a Staff tag that has been applied to an article.
  • Adding a Top Level tag to an article without completely tagging said article.
  • Adding a tag that is not found on the Tech Hub Tag List.
  • Adding a tag to an article that doesn't follow the rules stated in the Tech Hub Tag Page.
  • Removing any valid tags on an article.

What are the different types of tags?

As of the writing of this guide, there are currently 588 tags utilized on the SCP wiki. Due to the large amount, and constant addition of new tags, this guide will not attempt to explain every tag on the wiki, but will attempt to explain what the different tags are and what they are for. If you are looking for a more comprehensive guide which defines every tag, then look at the Tech Hub Tag List (the source of truth are the formal definitions in the Tag List Manifest).

SCP Attribute and Object Class tags are only applicable to SCP articles. For more information on tagging tales, refer to the Tale Tagging Guide for a list of Genre, Theme, Setting and Style tags. For more information on tagging artwork, refer to the Art Tagging Guide for an illustrated list of Style and Content tags.

SCP Attribute

Attribute tags are used to denote different aspects of an SCP, such as what it is made of, where it can be found, and what it can do. Only SCP articles can be given these tags, and incorrect application of these tags will warrant a tagging infraction.


If an SCP article about a singular live bee that can control reality was posted to the site, then it would be given the following tags:

  • animal — SCP is or exhibits traits of animal life.
  • alive — SCP is alive, meaning it exhibits traits of metabolism, reaction, and reproduction.
  • insect — SCP is or is related to insects.
  • airborne — SCP lives in, moves through, or spreads through the air.
  • ontokinetic — SCP is capable of manipulating reality through anomalous means.

(Note) Attribute tags make up the bulk of tags on the site, and an SCP article must be tagged with all attributes that apply before being considered complete. Application of major tag before this has been done will warrant a tagging infraction.

SCP Object Class Tags

Object Class tags are used to denote the object class of an article. If an article is given the object class safe, euclid, keter, thaumiel, archon, apollyon, ticonderoga, explained, neutralized, decommissioned or pending, it will be given the respective tag. If it is assigned a class other then the tags mentioned previously, then it will be tagged as esoteric-class. Only SCP articles can be given these tags, and incorrect application of these tags will warrant a tagging infraction.


Alright, lets give our bee a class. Because it is just a singular bee, then it is likely it can be contained in a normal enclosure, so it will be tagged as:

(Note) If an article has its object class changed throughout an article, then it will be tagged with its final object class. Two different object class tags should never be applied to a single article.

Character / Location Tags

These tags are applied to articles that contain a character, or setting that exists within the Foundation universe. The respective character, or setting must be featured significantly in the article in order to qualify for a tag. These tags can be applied to SCPs, Tales, and GOI Formats.


Using our example from earlier, If our bee was researched primarily by Dr. Alto Clef, and the article features a log that takes place in the city of Three Portlands, then it would be given the following tags:

  • doctor-clef — The article features Dr. Alto Clef as a primary focus.
  • three-portlands — The article features the city of Three Portlands.

(Note) There is no limit to the amount of location, or character tags an article can have. However, they must be prominently featured in the article in order to qualify.

Group / Canon Tags

These tags are given to articles that exist within a canon listed on the Canon Hub, or contains a prominent Group - typically a Group of Interest (GoI), although Foundation Departments and Mobile Task Forces can also be give their own Group tags. The article must have a significant connection to a canon or Group in order to qualify for its respective tag. These can be applied to SCPs, Tales, and GOI Formats.


Now, if our singular live bee was also discovered within a MC&D auction house, and the article was set primarily in the Broken Masquerade canon, then it would also be given the tags:

(Note) If the article is a GOI Format that appears on the GOI Formats Hub, then it will be applied with its respective hidden tag. For example, the MC&D GOI Format will be assigned the tags marshall-carter-and-dark and _marshall-carter-and-dark.

Staff Process / Major Tags

These are tags that are utilized by staff in order to facilitate work on the SCP wiki. This category also includes tags that are only applied to articles that have been fully tagged and authorized by a member of the tagging sub team.


However, incorrect application or removal of these tags will warrant a tagging infraction.

  • fragment — A page that is designed to be imported onto a single page.
  • _image — An article containing an image that needs to be checked for license compliance.
  • _licensebox — Used to mark an article that is utilizing a licensebox.
  • co-authored — Used to mark an article that was written by multiple users.


The application of these tags to articles that have not been completely tagged and/or their removal from pages that have been completely tagged will result in a tagging infraction.

  • scp — The article is an SCP.
  • goi-format — The article is a GOI Format.
  • tale — The article is a Tale.
  • joke — The article is a Joke SCP, or Tale.
  • explained — The article is an Explained SCP.
  • 001-proposal — The article is a 001 Proposal.
  • creepypasta — The article is a Creepypasta.
  • supplement — The article is a page which requires context from their parent page to understand.
  • site — The article is a Site Dossier.
  • author — The article is an Author page.
  • artwork — The article is an Art Hub.
  • essay — Articles that contain useful information on specific topics that may be helpful to authors.


The application or removal of these tags by non staff will result in a tagging infraction.

  • contest — Articles that are created for the purpose of community contests.
  • required — Guides that are part of the required reading for joining the SCP Wiki.
  • redirect — Pages which redirect the user to a different page.
  • featured — Reserved by staff for designating Featured Articles and Featured Tales.
  • prize-feature — Reserved by staff for designating articles featured by the winner of a site contest.
  • reviewers-spotlight — Reserved by staff for designating articles featured by a forum reviewer.
  • event-featured — Reserved by staff for designating articles featured on special event days such as International Talk Like a Pirate Day.
  • metadata — Reserved by staff for designating pages with structured meta information about articles.
  • archived — Pages which have been archived due to having been superseded, obsoleted, or inactivity.
  • in-rewrite — This is a temporary tag that indicates the article is currently being rewritten.
  • deletion-range — This is a temporary tag that indicates the article is currently being voted on for deletion.
  • deletable — This is a temporary tag that indicates the article has been voted on for deletion but not yet deleted.
  • _cc — This tag indicates that all images on the page in question are compliant with current licensing policy.
  • admin — Admin pages, as the name suggest, have some sort of official significance.
  • _theme-temp — Temporary tag used for marking old theme locations while they were moved from the component category to the theme category.
  • crosslink — This is a temporary tag that indicates the Wikiwalk Sub team of MAST is currently proposing revisions on the page, which should be seen in the comments.
  • guide — These pages are writing guides, helpful hints, or other pages intended to assist authors contributing to the site.
  • news — news pages contain news about the SCP Foundation ranging from new artwork by fans to recently posted successful articles and everything in between.

How do I tag a page?

You don't have to, and it is recommended you don't unless you have a firm understanding of the tagging rules and procedures. Members of the tagging sub-team will tag any article that is created, so if you see an article without tags, it is best to leave it blank. If you would like help by tagging your own articles, please familiarize yourself with the tagging rules stated in this guide, read the Comprehensive Tag Guide, and the Tech Hub Tag List thoroughly, and then contact a member of MAST with your suggestions. If they give you the go-ahead, feel free to apply them to the article.

I have an idea for a tag!

If you would like to propose a new tag to bee added to the Tech Hub Tag List, then you will need to gather a collection of articles that would meet the criteria for the new tag, and then propose the addition to either the Tag Proposal Forum. A member of the Technical Team will look over the proposal and either approve, or deny the request. The following are the requirements for adding a new tag.

Group Tag: The proposal must include 5 articles by 3 authors that feature the Group of Interest, Foundation Department or Mobile Task Force as a primary focus. It is recommended that proposals have 10 articles by 5 authors.

Character Tag: The proposal must include 5 articles by 3 authors that feature the character as a primary focus. It is recommended that proposals have 10 articles by 5 authors.

Location Tag: The proposal must include 5 articles by 3 authors that feature the character as a primary focus. It is recommended that proposals have 10 articles by 5 authors.

SCP Attribute Tag: Attribute tags have a higher expectation of applicable articles in order to be considered. The tag must cover a minimum of 15 articles, and it must also be distinct enough to the point where another existing tag, or combination of tags would not cover the articles in question.

Object Class: Object classes require a minimum of 25 articles to be approved, but there is no author requirement.

Genre and Theme Tags: Require a minimum of 25 articles by any author.

Art Tags: Require a minimum of 25 articles by any artist.

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License