protocols.io (concept)

protocols.io is a free, open platform for developing, versioning, and sharing detailed step-by-step research method protocols. It has been part of Springer Nature since a July 2023 acquisition, following a year-long pilot partnership, and now serves as the home for Springer Nature’s fully open protocols (including protocols migrated from the earlier Nature Protocol Exchange service). Researchers write a protocol directly on the platform — as a structured, numbered sequence of steps rather than free-form prose — and can attach reagents, equipment, timers, warnings, and file attachments to individual steps. Publishing a protocol assigns it a DataCite DOI, making that exact version of the method citable, discoverable, and persistently retrievable, independent of whatever journal article the method eventually supports.

How protocols.io works

Three mechanics distinguish protocols.io from simply posting a methods PDF somewhere:

• Version control. A protocol can keep evolving after publication — each edit creates a new version with its own timestamp, while the DOI’d version a paper cites stays exactly as it was when cited. A reader can retrieve the precise steps used in a specific study years later, even if the lab has since improved the method.
• Forking. Other researchers can “fork” a published protocol — copy it as a starting template and adapt it to their own equipment, organism, or reagents — while the platform keeps a visible lineage back to the original. This is closer to how software version control works than to how a conventional methods section is reused (copy-paste with no traceable link back to the source).
• Interactive run records. Beyond the static published protocol, protocols.io lets a lab keep a private, timestamped “run” record of executing that protocol on a given day — comments, deviations, and an integrated timer — which supports internal lab-notebook practice without being part of the citable public version.

Protocols on protocols.io are not peer reviewed by the platform itself — it functions closer to a preprint server for methods than a journal. Some protocols are formally peer-reviewed and published as protocol papers elsewhere (for example, in Nature Protocols or Bio-protocol) with a corresponding entry hosted on protocols.io; many others are deposited directly by the authoring lab with no independent review. A research office assessing a specific protocol’s rigor should check whether it carries an associated peer-reviewed protocol paper, rather than assuming DOI issuance implies review.

How it differs from a data repository like Zenodo or Figshare

protocols.io is frequently confused with generalist data repositories because both mint DataCite DOIs and both support open research practice — but they solve different problems and are not substitutes for each other:

• What’s being deposited. A Zenodo or Figshare deposit is typically a dataset, software release, presentation, or other research output — a fixed artifact. A protocols.io entry is a method: the reusable, step-by-step procedure used to produce or process that output. Neither generalist repository is built for structured, step-numbered method authoring, forking, or run-tracking; protocols.io was purpose-built for exactly that.
• Structure of the record. Zenodo and Figshare accept largely unstructured file uploads with descriptive metadata attached. protocols.io protocols are semi-structured documents — discrete, ordered steps that can each carry their own reagents, durations, and attachments — which is what makes forking and step-level commenting possible.
• They are complementary, not competing. A single study routinely cites both: a Zenodo or Figshare DOI for the raw dataset or analysis code, and a protocols.io DOI for the method used to generate it. CASRAI’s own generalist repository entry covers the Zenodo/Figshare/Dryad category directly; protocols.io sits outside that category as a discipline-focused method repository, per its own re3data.org registration (life-sciences focus, DOI-based, formerly operated as ZappyLab before the Springer Nature acquisition).
• Not the same as a protocol paper. A protocol paper (e.g. a PRISMA-P systematic-review protocol or a SPIRIT clinical-trial protocol) is a peer-reviewed publication that describes a planned study’s methodology, usually before the study runs. A protocols.io entry is the platform record of the method itself, and can exist with or without an accompanying protocol paper.

Why it matters for research administrators and reproducibility

Method-level detail is one of the most common places reproducibility breaks down: a results paper’s methods section is routinely too compressed — by journal word limits — to let another lab actually repeat the procedure. protocols.io addresses that gap directly, and it intersects with research administration in a few concrete ways:

• Journal and publisher integration. As a Springer Nature product, protocols.io is directly integrated into Nature Protocols and searchable through Springer Nature Experiments, and other publishers (e.g. GigaScience/GigaByte) support publishing peer-reviewed protocol papers alongside a protocols.io deposit. Authors preparing a submission are increasingly asked, or choose, to link a citable protocols.io DOI from the methods section rather than relying on prose alone.
• Grant and data management plan (DMP) relevance. A data management plan that addresses method transparency and reuse can point to protocols.io as the intended destination for detailed protocols, distinct from the repository named for the underlying datasets — research offices reviewing DMPs should not treat “we will deposit our data” as covering method documentation as well; they are separate deposits with separate purposes.
• Supports, rather than replaces, formal reproducibility infrastructure. protocols.io addresses the specific failure mode of an underspecified methods section; it does not on its own address workflow/software reproducibility (see CASRAI’s reproducibility infrastructure guide) or study preregistration (see preregistering a study protocol). A research office building a reproducibility checklist should treat method documentation, code/workflow sharing, data deposit, and preregistration as four related but distinct requirements, not one bucket.
• Free at the point of use. Individual authors and readers use protocols.io at no cost (no article-processing charge, no subscription); institutions can also run paid team/workspace plans for managed lab or department accounts, which is the detail a research office comparing costs against a data-repository budget line needs to check separately, since the free public tier and an institutional plan are different products.

Examples

• A wet-lab researcher publishes a CRISPR knock-in protocol on protocols.io, receives a DOI, and cites that DOI in the methods section of a subsequent journal article rather than reproducing every step in the text.
• A second lab forks that published protocol, adjusts the reagent concentrations for a different cell line, and publishes its own forked version with a new DOI — while protocols.io preserves the visible link back to the original.

Counter-examples

• A dataset deposited on Zenodo or Figshare is not a protocols.io entry — it is a fixed research output, not a versioned, forkable method.
• A methods section published inside a results paper, with no separate DOI or platform record, is not a protocols.io deposit.
• A peer-reviewed protocol paper (PRISMA-P, SPIRIT) is a distinct publication type from a protocols.io entry, even though the two are often linked.

References

• Springer Nature Group, “Publisher acquires protocols.io, driving open research” (press release, 26 July 2023).
• Nature Protocols, “Welcoming protocols.io” (editorial, 2024).
• re3data.org, protocols.io repository record (r3d100013705).