How long does Wikipedia draft review take?

How long does it take for a Wikipedia draft to be reviewed?

There is no fixed answer, and Wikipedia does not promise one. Its Articles for Creation page says plainly that there is no fixed waiting time, that some drafts are reviewed quickly while others wait considerably longer, and that drafts are not necessarily reviewed in the order they were submitted.

The nearest thing to an official figure is the yellow notice that appears on a draft once it is submitted. It reads "Review waiting, please be patient", followed by an estimate and the size of the queue. When we checked it in late October 2026, it said the review "may take 7 weeks or more, since drafts are reviewed in no specific order", and that there were 3,458 pending submissions waiting.

That estimate changes from week to week, so treat any number you read elsewhere, including this one, as a snapshot. The notice on your own draft is always the current figure.

How is the waiting time on the notice worked out?

It is calculated automatically from the age of the oldest drafts still waiting. Every pending submission is sorted into a category by how long ago it was submitted, and the template that writes the notice checks those categories from the oldest down. The first one that holds drafts sets the wording.

So the notice describes the tail of the queue. If a handful of difficult drafts have been passed over for weeks, the estimate lengthens even while many newer submissions are being reviewed within days. That is why two people who submitted on the same day can have very different experiences.

Why are drafts not reviewed in the order they were submitted?

Because the reviewers are volunteers who choose what to pick up. Wikipedia's frequently asked questions for Articles for Creation say that some reviewers work through the oldest submissions, while others review subjects they know. Reviewers are under no obligation to review any particular draft, and the same page points out that Wikipedia has no deadlines.

A reviewer has to read the draft, open the sources, judge whether they amount to significant independent coverage and check the writing for neutrality and copying. A short draft on a clear subject with three strong sources is quicker to assess than a long draft with forty references, half of them passing mentions. Nothing in the process rewards length.

Two things Wikipedia specifically asks you not to do:

• Resubmit the same draft repeatedly. It does not move it up, and Wikipedia warns that resubmitting without addressing the problems may become disruptive.
• Ask individual reviewers to look at it quickly. The help pages say this will not make the process faster.

How do you submit a Wikipedia draft for review?

Click the "Submit the draft for review!" button on the draft. If the button is missing, open the draft in the source editor, add {{subst:submit}} at the very top, and publish the change. A submission box should then appear at the top of the draft. If it does not, the Articles for Creation help desk can sort it out.

Three points cause most of the confusion:

• "Publish" is not "submit". The publish buttons only save your work. A draft stays a draft until it is submitted and accepted, or moved into the article space another way.
• A sandbox draft can be submitted where it is. It does not need to be moved to a title beginning Draft: first. If it is accepted, the reviewer moves it to a suitable title.
• Formatting is not required. An infobox, images, categories and perfect layout are not conditions of acceptance. Reviewers look at notability, sources and neutral writing.

Once submitted, you can keep improving the draft. Adding better sources or correcting mistakes does not require a fresh submission, as long as you publish each change.

What happens when a reviewer reaches your draft?

The reviewer accepts, declines or rejects it. Acceptance publishes the draft as an article. A decline means the draft is not ready but the problems may be fixable, and it can be improved and resubmitted. A rejection means the reviewer considers the subject or content fundamentally unsuitable, and the draft should not be resubmitted unless significant new evidence appears.

A decline comes with a reason, such as insufficient evidence of notability, an advertising tone or inadequate sourcing. There is also a decline reason for drafts that appear to contain text generated by a large language model, which is covered in our guide on whether ChatGPT can write a Wikipedia article.

Each review notice stays on the draft. Wikipedia asks authors not to remove or alter earlier notices, because they show later reviewers what has changed. A resubmitted draft goes back into the same queue, and a different reviewer may pick it up. If you have had a decline, our guide to a declined Wikipedia draft explains how to read and answer it.

What happens after a draft is accepted?

The draft is moved into the article space, and in most cases it enters a second queue: new page patrol. Every new article appears in Wikipedia's new pages feed, where reviewers with the new page reviewer right check it again. If the reviewer who accepted the draft holds the new page reviewer or autopatrolled right, they are allowed to mark it as reviewed at the same time, although Wikipedia's instructions suggest leaving borderline cases for a second pair of eyes.

Until an article is marked as reviewed, Wikipedia tells search engines not to index it. That restriction lifts when the article is reviewed or when it is 90 days old, whichever comes first. A newly accepted article can therefore exist on Wikipedia for weeks without appearing on Google. Our guide to a Wikipedia page not showing on Google explains the rule in full.

That second queue can be long. In late October 2026, the backlog figures shown on Wikipedia's statistics page put the number of unreviewed articles at just over 30,000, with the oldest dating back eight years.

Why is acceptance at Articles for Creation not the end?

Because acceptance is one reviewer's judgement, and every article stays open to the rest of the community. Wikipedia's own guidance to authors says that an unsuitable article may be returned to draft space or nominated for deletion.

In practice, an accepted article can meet any of these:

• Tagging. A new page reviewer or any other editor can add maintenance tags for sourcing, tone or a suspected conflict of interest.
• Draftification. A new article judged not ready can be moved back to draft space. Wikipedia's new page patrol guidance says this should not be done to articles older than 90 days.
• Deletion. Any article can be proposed for deletion or taken to Articles for Deletion, whatever route it came in by. Our guide to Articles for Deletion explains what that involves.

The strongest protection is an article that clearly meets the standard when it is accepted, so that later reviewers have nothing to question. A draft that scraped through on a generous review is the one most likely to come back.

Can you skip the Articles for Creation queue?

Technically, some editors can, but the people most anxious about the wait usually should not. Articles for Creation is optional for an autoconfirmed account, which can create an article directly or move its own draft into the article space. Wikipedia's help pages still advise new article creators to leave the draft submitted for review.

The position is different for anyone writing about themselves, their employer or a client. Wikipedia's Articles for Creation page says that editors with a conflict of interest or who are paid to edit should submit drafts through the process and follow the disclosure requirements. New page patrol guidance tells reviewers that an article created outside the process by such an editor may be moved to draft space and sent back through it. Bypassing the queue in that situation tends to add a step, not remove one.

No one can buy a faster review. Wikipedia's scam warning says it does not charge to submit, review or publish articles, and that anyone promising guaranteed publication or special treatment for money is not acting for Wikipedia.

Is the waiting period something to manage on your own?

For a well-prepared draft, yes. If the sources are strong and the writing is neutral, the only thing left is time, and the queue does not move faster for anyone. Use the wait to tighten the draft rather than to chase reviewers.

The real cost of the wait shows up when a draft is declined. Each decline usually means another spell in the queue, and every notice stays on the draft for the next reviewer to read. A draft that takes three rounds to get through can spend months in review and arrive with a visible history of problems, which is the opposite of the clean record a new article benefits from.

That is where experience matters most: judging before the first submission whether the sources will carry it, and writing it so the first reviewer has no reason to decline. Our Wikipedia article creation work is built around getting that first review right. If a draft is already in the queue or has been declined, a free page health check will tell you what a reviewer is likely to see.