PLOS ONE Submission Process

Most journals evaluate papers on significance and novelty. Editors ask: is this important enough for our readers? Will it change the field? PLOS ONE doesn't ask those questions. The editorial criteria are technical: Is the science sound? Are the methods appropriate? Are the conclusions supported by the data?

That's not a lower bar: it's a different bar. A paper with modest scope but rigorous methodology belongs in PLOS ONE. A paper with an ambitious hypothesis but underpowered statistics doesn't. If you misread PLOS ONE as a fallback journal where "anything goes," you'll get desk rejected for scope mismatch and never understand why.

The journal publishes across all disciplines: biology, medicine, chemistry, physics, social sciences, computational fields. It's intentionally discipline-agnostic. That means a rejection almost never comes down to field fit. It comes down to methodology and rigor.

When you submit, a PLOS ONE academic editor: typically a researcher in your field: does an initial desk review. This is not a quick skim. They look at specific things:

Methods and reproducibility. PLOS ONE has strict reporting requirements. Clinical trials need CONSORT compliance. Animal studies need ARRIVE compliance. Observational studies need STROBE. If your study type has a reporting checklist, you need to follow it. Missing compliance is one of the most common desk rejection triggers.

Statistical adequacy. Underpowered studies get flagged at the desk stage. If you ran a study with n=12 and claim significant results, expect pushback before external review even begins.

Data availability. PLOS ONE requires that supporting data be available to reviewers and readers. Proprietary datasets with no access statement, or data available "upon reasonable request" without a formal repository link, will slow your paper or get it rejected outright.

Ethics documentation. Human subjects research needs IRB approval documentation. Animal research needs IACUC or equivalent. These aren't optional: they're required fields in the submission system.

Software and code. If your analysis relies on custom code, you're expected to make it accessible. A GitHub link is fine. "Code available on request" is not.

PLOS ONE routes every submission through four stages on Editorial Manager. Knowing which one you are in tells you what the hold-up is.

Initial Quality Check

A staff administrative check runs first: file completeness, plagiarism screen, authorship and competing-interests declarations, ethics fields, and whether the required reporting checklist and data availability statement are present. This is where most fast administrative returns happen.

Editorial Assignment

An academic editor (a researcher in your field) is assigned and does the desk review, deciding whether the manuscript is sound enough in scope and method to send for external review.

Peer Review

PLOS ONE uses single-blind peer review, sending the paper to two external reviewers (occasionally three) who assess soundness, statistics, reporting, and data, not novelty. PLOS ONE also offers an optional published peer review history, an open peer review feature where the review record is published alongside the accepted article.

Final Decision

The academic editor weighs the reviews and issues the decision: accept, minor revision, major revision, or reject.

Day-by-day editorial timeline

Total time from submission to published article is about 4 to 8 months for a straightforward paper. The first decision usually lands in 6 to 8 weeks, though complex, contentious, or hard-to-referee papers are an exception and can run noticeably slower when an editor struggles to recruit reviewers.

If your paper sits at desk review for more than 3 weeks with no action, you can email the editorial office to ask about status; the academic editor assigned to your paper, and their current workload, is the single biggest source of timeline variance.

PLOS ONE sends papers to 2 external reviewers, occasionally 3. The review criteria mirror the desk review: they're not judging whether this is the most exciting paper of the year. They're assessing whether it's technically correct.

The structured review form asks reviewers to evaluate:

• Study design and statistical analysis: appropriate methods for the research question?

• Reporting of key results: complete and accurate presentation of findings?

• Discussion and conclusions: do they stay within what the data support?

• Adherence to reporting guidelines: are the appropriate checklists followed?

• Ethical compliance: proper documentation of approvals?

Reviewers are explicitly told NOT to reject based on perceived significance or expected citation impact. In practice, experienced PLOS ONE reviewers stick to this. You'll rarely get a rejection that says "this isn't novel enough." If you do, that's inappropriate and you can flag it to the editor.

Based on patterns across the literature and author reports, the most frequent PLOS ONE desk-rejection failure patterns fall into these categories:

Reporting guideline violations. CONSORT, STROBE, ARRIVE, PRISMA: missing or incomplete compliance is probably the single most common fixable rejection reason. Download the relevant checklist and fill it out completely before submission.

Check whether your PLOS ONE reporting checklist maps to real manuscript text →

Inadequate statistical power. Small sample sizes without a priori power calculations, or post-hoc tests that don't account for multiple comparisons, consistently get flagged. If your study is exploratory by nature, frame it that way explicitly.

Check whether your PLOS ONE sample-size rationale is defensible →

Missing data availability statement. Not just vague: PLOS ONE needs a specific statement about where data are deposited and how to access them. Figshare, Dryad, Zenodo, a journal supplement, or a GitHub repository all work. "Available on request" has been unacceptable since 2014.

Check whether your PLOS ONE data availability statement is concrete →

Ethics statement issues. Missing IRB/IACUC number, incorrect committee name, or absent consent statement for human subjects work will trigger an immediate request or desk rejection.

Out-of-scope conclusions. If your abstract or discussion makes claims that go beyond what your data support, editors flag it. PLOS ONE reviewers are specifically trained to catch overreach.

The key shift when writing for PLOS ONE is to make your rigor visible. Don't bury methodological decisions in the methods section: explain them. If you chose a sample size for a specific reason, say so. If you pre-registered the study, link to it prominently.

For the abstract, structure it tightly: background, objective, methods summary, key results (with numbers), and conclusion. PLOS ONE abstracts are indexed and read in isolation: make every sentence count.

For the discussion, stay close to your data. The PLOS ONE reviewer's checklist includes a specific item about whether conclusions are supported by the presented results. If you extrapolate significantly, expect a revision request.

PLOS ONE currently offers format-free initial submission, so the process risk is not whether the first upload already follows every final production rule. The bigger risk is whether figures, tables, and supporting files make the methods, data, and conclusions inspectable. Treat formatting flexibility as time saved, not permission to submit a loose evidence package.

PLOS ONE's APC is $2,477 USD. This applies to all accepted papers. PLOS has institutional agreements with many universities that reduce or eliminate this cost: check the PLOS institutional account program before worrying about paying out of pocket. Many authors at US and European institutions pay nothing.

For authors without institutional support, PLOS ONE offers fee assistance and waivers. The waiver process is straightforward and based on self-reported financial need. If cost is an issue, apply: the journal approves most waiver requests.

PLOS ONE's data policy is stricter than most journals, and it trips up authors who aren't prepared. The requirement is straightforward: all data underlying the findings must be fully available without restriction at the time of publication. "Available upon reasonable request" hasn't been acceptable since 2014. Here's what that means in practice.

The exception pathway exists but it's narrow. If your data genuinely can't be shared publicly, patient-identifiable information, indigenous community data with restricted governance, or data owned by a third party, you must explain this in your Data Availability Statement and provide a contact point for access requests. PLOS ONE's editors review these exceptions case by case. Weak justifications ("our institution doesn't allow it") get rejected. Strong justifications ("data contain identifiable patient information; de-identified datasets are available from the specific contact") get approved.

Prepare your data availability statement before you write the paper, not after acceptance. Depositing data in a public repository takes time, especially if your institution has data governance requirements.

Most PLOS ONE papers don't get accepted on the first round. The typical path is one to two revision rounds, with a small percentage requiring three. Understanding what each round usually involves helps you budget time and avoid unnecessary delays.

The most common revision requests follow predictable patterns. Statistical concerns top the list: missing power calculations, inappropriate tests for the data type, or uncorrected multiple comparisons. Methods detail is second, PLOS ONE's reproducibility standard means reviewers want enough information to replicate your exact procedure. Reporting checklist compliance is third, especially for clinical or animal studies where CONSORT, STROBE, or ARRIVE checklists are required.

How to respond efficiently: create a response document with numbered entries matching each reviewer comment. Quote the comment, state what you changed, and give the exact page/line numbers. Don't argue with reviewers unless they're factually wrong, if a reviewer asks you to justify a statistical choice, justify it rather than explaining why the question is unnecessary. Academic Editors read the response letter as carefully as the revised manuscript. A clear, systematic response that addresses every point (even minor ones) signals professionalism and usually leads to faster acceptance.

A PLOS ONE submission readiness check can identify the statistical, methods, and reporting issues that PLOS ONE reviewers most commonly flag.

Across Manusights submission reviews for biomedical, social-science, ecology, methods, and interdisciplinary manuscripts targeting PLOS ONE, the most important submission failures come from confusing "no novelty requirement" with "loose evidentiary review." PLOS ONE current guidelines allow flexible length and do not reject only because a study lacks perceived impact, but the same guidelines are strict about manuscript organization, Materials and Methods detail, statistical reporting, data reporting, study-type requirements, ethics, cover letter content, and conclusions that stay within the evidence.

We reviewed 100 recent published PLOS ONE papers when this guide was built, then compared those published packages with Manusights internal analysis of soundness-first submissions prepared for PLOS ONE, Scientific Reports, BMC journals, Frontiers journals, and specialty open-access venues. That comparison is why the patterns below focus on reporting traceability, data access, and conclusion strength rather than impact-factor or APC trivia.

Pattern 1: Reporting checklists are attached but not traceable inside the manuscript

For manuscripts targeting PLOS ONE, the most common soundness-first failure is a checklist package that looks complete as a file upload but is not actually traceable through the manuscript. PLOS ONE asks authors to follow study-type requirements for clinical trials, observational studies, animal research, systematic reviews, meta-analyses, qualitative research, paleontology, cell lines, antibodies, software, and many other article categories.

The portal may accept a CONSORT, STROBE, ARRIVE, PRISMA, or other reporting checklist, but the academic editor still has to see the corresponding information in the abstract, methods, results, figures, tables, and supporting information.

The weak version is a checklist with "yes" boxes while the manuscript omits allocation concealment, blinding, eligibility criteria, inclusion dates, animal housing conditions, prespecified outcomes, missing-data handling, subgroup definitions, software versions, or protocol changes. This is not a novelty problem. It is a reproducibility and reporting problem. A PLOS ONE paper can be technically sound and still slow down or fail because the checklist, Materials and Methods, statistical analysis plan, ethics statement, figures, and supplementary files do not point to the same evidence.

The practical fix is to audit the manuscript by checklist item before upload, not after peer review. If CONSORT item language appears only in a PDF checklist and not in the methods section, the editor cannot verify it. If ARRIVE details are buried in supplementary information without clear main-text pointers, reviewers may treat the study as underreported. Scientific Reports, BMC journals, Frontiers journals, and discipline-specific society journals face similar reporting pressures, but PLOS ONE makes this especially visible because soundness is the central editorial contract.

Pattern 2: The Data Availability Statement promises access the reader cannot actually use

For manuscripts targeting PLOS ONE, the second pattern is a data-access statement that sounds compliant but fails the practical reader test. PLOS asks for data reporting and has a dedicated Data Availability policy because reviewers and readers need enough access to verify the findings. The failure is rarely that authors forget to write a statement.

More often, the statement says data are "available upon request," stored behind institutional permissions, controlled by a commercial license, attached only after acceptance, or available from a generic corresponding-author email without a specific governance route.

The vulnerable manuscript components are the Data Availability Statement, methods section, results tables, figure legends, accession numbers, repository links, code files, and supporting information. For PLOS ONE, the claim in the abstract should be traceable to data that a qualified reader can inspect under the stated access conditions. If there are legitimate restrictions, such as patient-identifiable data or third-party-owned datasets, the manuscript still needs specific contact, ethics, and access language rather than a vague promise.

If the study uses software, protocols, sequence data, crystallography files, qualitative transcripts, or image data, those materials need a real availability plan before the Editorial Manager submission is started.

This pattern is dangerous because it can make a methodologically reasonable paper look less transparent than it is. A manuscript that might fit PLOS ONE, Scientific Reports, BMC Medicine, PeerJ, Frontiers in Public Health, or a specialty open-access journal can lose momentum if the data statement is drafted last. Build the statement from the figures backward: every figure and table should have a data source, access route, and restriction explanation where needed.

Pattern 3: Statistical and methodological support does not match the conclusion strength

For manuscripts targeting PLOS ONE, the third pattern is a mismatch between conclusion language and methodological support. PLOS ONE does not require a field-changing novelty claim, but it does require that the study is technically sound and that conclusions are supported by the data. Authors sometimes interpret the broad-scope policy as permission to submit a thin methods section, small sample, exploratory analysis, or observational association with causal language. That is where academic editors and reviewers tend to focus.

The key components are the abstract conclusion, Materials and Methods, statistical analysis plan, sample-size justification, controls, inclusion criteria, figures, tables, supplementary analyses, and limitations paragraph. A small study can fit PLOS ONE if the research question, power or precision rationale, model choice, covariate plan, and interpretation are proportionate. The same study becomes vulnerable when the abstract says "demonstrates," "proves," or "establishes" but the data only support association, feasibility, descriptive prevalence, or hypothesis generation.

The PLOS ONE submission guidelines ask for enough method detail to allow replication, and that means the methods section cannot rely on a citation for every operational choice.

Before upload, compare the final sentence of the abstract with the actual strongest result in the figures and tables. If the methods can support that sentence, the manuscript is much closer to PLOS ONE readiness. If not, retargeting to Scientific Reports, a BMC specialty journal, Frontiers, PeerJ, or a narrower disciplinary venue will not solve the underlying problem. The conclusion, methods, statistics, data availability, and reporting checklist need to tell the same soundness story.

Check whether your PLOS ONE manuscript is submission-ready

How this page was created: sources used include PLOS ONE submission guidelines, the PLOS ONE getting-started guide, PLOS ONE publication criteria, PLOS data-availability policy, the Editorial Manager submission portal, Clarivate JCR, SciRev author-reported timing, and Manusights internal analysis of soundness-first submissions prepared for PLOS ONE, Scientific Reports, BMC journals, and Frontiers journals. We did not test a private live PLOS Editorial Manager account for this page; upload and timing guidance is based on public PLOS materials, documented author experience, and pre-submission review patterns.

Source limitations: PLOS can update Editorial Manager fields, APC support rules, and policy pages after this review date, so authors should verify final administrative details against official PLOS pages before upload.

Official guidance explains the upload rules, publication criteria, and policy requirements. Authors still need a pre-upload judgment about whether the manuscript is technically sound but vulnerable on checklist alignment, data access, ethics language, sample-size justification, or conclusions that overrun the study design.

Use this guide for the current author decision gap competing pages often miss: PLOS ONE is flexible on novelty and initial formatting, but still strict about reporting guidelines, data availability, ethics language, and conclusions supported by the study design.

Why this page exists: the query "PLOS ONE submission process" is a workflow query with commercial intent. Authors are close to upload and need to know what will block the submission, what will slow first decision, and whether a soundness-first journal is the right home before they pay an APC.

In our analysis of PLOS ONE-targeted manuscripts, the named failure pattern is assuming "soundness-only review" means loose administrative review. The opposite is closer to the truth: PLOS ONE is forgiving about novelty, but strict about reporting guidelines, data access, ethics language, and conclusions that stay within the evidence.

What the process does well: It gives methodologically solid, non-field-defining work a legitimate broad outlet and removes novelty as a rejection reason.

Where the process is unforgiving: It exposes messy data-sharing plans, missing checklist alignment, weak power justification, and vague ethics statements before the paper reaches reviewers.

Use this page for upload workflow and editorial checks. Use PLOS ONE review time for timing-only intent, the PLOS ONE selectivity page for odds, and Scientific Reports vs PLOS ONE for journal-choice intent.

Submission steps and editorial requirements confirmed against the PLOS ONE submission guidelines, PLOS ONE getting-started guide, PLOS ONE journal information, and the Editorial Manager portal as of May 2026. Impact Factor 2.6, Q2, rank 44/135 in Multidisciplinary Sciences confirmed via JCR 2024.

Or see example reports before you finalize.