OSF Projects Transition FAQs

This Article Is Licensed Under CCO For Maximum Reuse.

General Questions
Timeline Questions
Technical Project Questions
Registration and Preprint Questions
COS, Sustainability, and Stewardship

General Questions

Why is COS making this change?

Maintaining OSF Projects’ flexible functionality is complex and costly, requiring COS to devote more resources to keeping existing services running and fewer to improving the OSF. Continuing at the current scope would require COS to raise approximately $4-5 million each year for the next several years. In the current funding environment, we cannot plan around that level of annual support over the long term.

At the same time, repositories and other research services have matured and are now purpose-built for many of the functions OSF Projects provided. Phasing out OSF Projects allows COS to reduce that maintenance burden, focuses OSF on the areas where it can contribute most, and work alongside other open research services rather than duplicating what they already do well. This is both a response to financial reality and a decision about responsible stewardship and mission. Read more about the history and rationale behind this decision.

What will the OSF be going forward?

The OSF will continue as a free, open-source platform for creating and linking transparent research records. Researchers can use OSF to register study plans, publish Preprints through community-run services, and link those records to related data, materials, code, publications, and other results stored in other repositories or systems. OSF's new Project Workflow Launcher helps guide users to the best tools for their objective: registries, Preprints, searching for content, or looking into other platforms for sharing research data.

OSF will no longer function as a general project collaboration, data repository, or file management space. Going forward, COS will focus OSF on making it easier to document what was planned, connect that plan to what the research produced, and link the results that were ultimately reported. This more focused role allows OSF to work alongside repositories and other research services rather than duplicating the functions they are better positioned to provide. Read the OSF product roadmap to learn more.

Am I required to make any changes to my OSF content?

No. All changes on your part are voluntary. Public content stored on the OSF will not be altered. If your public Project does not need further updates, we strongly recommend that you take no action: the OSF will continue to provide access and manage storage and preservation for your Project.

It is your decision and responsibility to decide if content that is private should be made public or removed from the OSF.

If you are still actively using your Project space and wish to migrate it to another repository, you may do so. Our help guides on downloading your content from OSF can help you manage that process. However, if your Project has been given a DOI, or you wish to have a URL redirected, you will need to consult this transition guide and take the appropriate steps.

Will my Project still be findable and accessible after February 19, 2027?

Yes. OSF Search will be unchanged and no links will change. Your public Projects will continue to be maintained and accessible via the OSF platform. Your private Projects will also remain available to anyone who has access as of February 19, 2027. To learn more about what is changing with OSF Projects, visit our OSF Projects Transition help guide.

What if I have a mix of public and private Components in my project?

All Projects and Components will become read-only on February 27, 2027, and access at current levels is maintained. Public Components will continue to be public and private Components will still be available to those who have access to them on that date.

After February 19, 2027, admins of private Projects or Components may make them public, but public Projects and Components may not be made private. Any Project or Component, private or public, may be deleted after February 19, 2027.

You are responsible for ensuring that the correct Components are private or public. Components are private by default upon creation.

You can find out more information about how changes to public and private Projects work in our OSF Project Transition Help Guide.

What other tools or platforms can I use as a replacement for OSF?

If you are still actively using your Project space and wish to migrate it to another repository, you may do so. There are two parts to this process. The first is to download the content and metadata from your Project. You can find help with this process in our guide for downloading OSF content.

The second is to decide on a new location for storing your OSF Project content. Depending on the type of content, you may want to make different selections. Go to What Do I Do With My Research Content or What Do I Do With My Non-Research Content for more guidance.

If you move your content to another repository, it is best to fully remove the content from OSF so that it is not duplicated. Once you have uploaded content in a new location, follow the directions to request that your original URL or DOI be redirected to the new location.

Will the DOI or URL for my Project change?

If you choose to leave your content on the OSF, it will be archived as a Read-Only Project and will remain accessible at the same URL and DOI, if one was created. If your public Project does not need further updates, we strongly recommend that you take no action to ensure that these identifiers and links remain correct.

If you wish to move your content, you can request that OSF redirect any traffic to the new URL. If you have not yet created a DOI for your content, the best path would be to move your content to another repository to create the DOI there. If you have already created a DOI for your work in OSF, follow the instructions in our guide to request a redirect to your new DOI.

I put the OSF in my data management plan (DMP) for a current or upcoming Project. What should I do?

Your first step should be to update your DMP with new information once you determine the best place for your data. If you already have an existing OSF Project where you’ve identified that the data will be deposited, update the Project description with a link to a new data repository where the data will be stored. Ideally that link will be to a specific new page, but if that is not yet possible, simply mentioning the name (e.g. Zenodo, or Dryad) is sufficient. If you do not already have a specific OSF Project, you can update your DMP when you have made your decision about where to share the forthcoming research outputs.

I put the OSF in my consent forms/IRB application for a current or upcoming Project. What should I do?

We recommend contacting your local ethics review board, funding agency, etc. for guidance on how to navigate any needed changes to your study related to data storage and sharing. See our guide on managing funder and institutional requirements for more information.

Timeline Questions

Can I still add content to my existing Projects until February 19, 2027?

Yes, all existing OSF Projects will be editable until February 19, 2027. You can edit metadata, change contributors, add files, change wikis, and change content in storage add-ons. Starting on November 16, 2026, however, you will no longer be able to create any new Projects or Project Components. See the transition guide for more information.

Can I still create new Projects or Components within Projects until February 19, 2027?

Only until November 15, 2026. After this, you will no longer be able to create new Projects or add child Components to existing Projects through any OSF page or API. See the transition guide for more information.

If my Project is private, can I switch it to public after February 19, 2027?

Yes, private content can be made public or deleted after February 19, 2027. You are responsible for ensuring that the correct Components are private; Components are private by default, but could have been made public at some point. See the transition guide for more information.

If my Project is public, can I switch it to private after February 19, 2027?

No, public content cannot be made private, but it can be deleted. Scholars will need to ensure that the correct Components are public; just because a parent Project is public does not mean the Components are, too. If you need to talk to someone about a public Component that needs to be private after February 19, 2027, please contact support@osf.io for assistance.

Will I be able to update my metadata after February 19, 2027?

No. The only updates that will be possible to Projects after this date will be to delete them from OSF, or to switch them from private to public. See the transition guide for more information.

What functions will still be available on the platform after February 19, 2027?

Registration and Preprint workflows are unaffected by these changes, however they are not meant as replacements for Project storage. Registration workflows are meant to document study plans and outcomes, while Preprints are meant to help researchers share their research results. See our guide on Registrations for more information.

Technical Project Questions

How do I download the files or other content like wikis and activity logs from my Projects?

Please reference our guide on downloading content from OSF Projects and Components for more information.

How do I update a DOI or redirect a URL to my Project if I choose to remove my content from OSF and put it somewhere else?

What if I’ve shared a view-only link to a private Project for peer review?

View-only links will still work while private Projects are in the read-only state. If you have created anonymous view-only links, they will also work, but be aware that reviewers can access your content outside of the view-only mode if the content is public. Once your peer review is complete, you can make your Project public. See our guide to view-only links for more information.

You will no longer be able to create view-only links for Projects after February 19, 2027.

Will analytics still be tracked for my Project?

Yes, analytics will continue to be tracked using current functionality.

If I linked an add-on in order to give access to users, will those users still have access after the Project is read-only?

Yes, Read-only access to Project add-ons will be maintained. Any changes that might have been possible through the OSF interface such as uploading new versions of files will no longer be possible. Find out more about how the transition affects add-ons in our add-on guide.

How will the changes to OSF be represented in the OSF API?

The OSF API remains an open way to access the Projects, Registrations and Preprints on the OSF. However, after November 16th 2026 and February 19, 2027 many GET and POST functions will be deprecated. Find out more details about changes to expect in OSF Projects API Impact.

I have an account/multiple accounts I can’t get into. What happens to that material?

If you have access to both accounts, you can follow the instructions in our guide for merging accounts. If you do not have access to one or more of the accounts, contact support@osf.io for assistance.

What about content created by deceased users?

In cases where and there is a need to gain access to the data of a deceased individual, a contributor or individual who is requesting access must provide:

A link to an obituary or news article OR copy of a death certificate (scanned is fine)
Legal proof (letter from next of kin or legal representative) that they should have access to the deceased users’ data OR If deceased user was affiliated with an institution or organization provide a letter from the Department or Institution saying that this is a reasonable access request, and requestor should be granted access

Please send an email to support@osf.io with [Request for Access] in the subject line and the listed documents attached.

Registrations and Preprints

What is the difference between a Project, a Registration, and a Preprint?

OSF Projects, Registrations, and Preprints represent three different things in OSF.

Project: a flexible space for a researcher and collaborators to organize, aggregate, and share research materials before, during, and after research activities. This service is being sunset.
Registration: a structured service for recording the plans and details of a research study, ideally before data gathering or analysis has begun. Changes to Registrations are tracked to create a transparent record over time. This service will continue.
Preprint: a research paper that's shared publicly without going through an official peer review process. OSF Preprints are moderated by sponsoring communities to ensure the appropriateness of the content within the community's scope, but not edited or revised. This service will continue.

Will I still be able to create a Registration from a Project?

No. The ability to create a Registration from an OSF Project will no longer be enabled after February 19, 2027.

What happens to Projects that are linked as supplemental materials to my Preprint?

Links to OSF Projects will remain unchanged. If you move your content, you are responsible for updating links to supplemental materials on your Preprints by requesting a redirect or utilizing the “Author Assertions” fields.

Can users simply switch to uploading their data and other materials via the Registration workflow?

No. Registrations are designed to document and share preregistrations, study plans, and similar practices. You should identify a data repository for sharing data, materials, and other supplements. See our guide on choosing a repository for more information.

Will I be able to include files from other storage integrations in newly created Registrations?

No. On February 19, Registrations can no longer be started from an OSF Project. Files can only be uploaded as part of the submission, or connected via the Resources metadata fields.

Will the 5GB limit still apply to Registrations?

Yes, the 5GB storage limit remains in place for all new Registrations.

What about DOIs from OSF Projects users linked to as Outputs on Registrations?

If you have used a DOI for content stored on the OSF as an output, it will continue to resolve. If you move your content, you are responsible for updating links for outputs on Registrations. See our guide on redirecting links for more information.

COS, Sustainability, and Stewardship

Where can I find OSF policies and official statements?

Several policies or statements are available on our various webpages:

If you are looking for another specific policy, check the COS page on Compliance and Standards or please contact us at support@osf.io.

How was this decision made?

The changes to OSF were determined through a combination of product strategy development and organizational financial forecasting over several months, and included consultation with the COS Board of Directors and key partners.

Did COS consider paid accounts, storage fees, or other alternatives?

COS is committed to providing public goods infrastructure that is free for users. Because there are other services that support use cases that will be removed from OSF, we maintained our commitment to public goods infrastructure rather than compete with those by shifting to a service that users pay to access or use.

How has COS used its funding, and what does the current financial outlook mean for the organization’s future?

As a charity, COS relies on a combination of donations, grants, and support from institutions to fund its services and broader mission. COS operates efficiently with the resources it receives; for example, its negotiated federal indirect cost rate for 2026 is 28.1%, which is substantially lower than that of many institutions.

COS’s funding supports not only OSF, but also research, policy advocacy, training, and community-building. Much of that funding comes through grants that are restricted to specific purposes and cannot be redirected to infrastructure. At the same time, OSF Projects’ flexible collaboration and storage functionality is complex and costly, and continuing to operate OSF at its current scope would require COS to raise approximately $4-5 million each year for the next several years. In the current funding environment, we cannot expect that level of annual support.

With significant uncertainty in the financial outlook for science in the United States, COS is proactively reducing the costs and complexity of its services and programs. COS is also incorporating in the E.U. as part of a broader strategy to strengthen the organization’s sustainability and continue advancing its mission.

How will COS ensure the long-term persistence of public OSF content, and what is its preservation plan?

We are committed to the persistence of the scholarly record by ensuring that publicly shared research objects and their associated metadata on OSF remain persistent, discoverable, and accessible through sustainable strategies and persistent identifiers.

As part of this strategy, OSF backs up public Registrations on the Internet Archive and we intend to extend this to public Projects and Preprints. To support long-term stewardship of the public OSF content, COS maintains a fund to ensure continuity of public content should the organization ever need to close or significantly curtail operations. We currently have committed $450k to this fund and evaluate this resource regularly as part of continuity planning.

You may have seen earlier COS materials refer to specific time estimates — such as 10, 20, or 50 years — for maintaining OSF content. Those estimates reflected an earlier approach in which COS estimated the cost of maintaining the storage itself in the event of a closure or significant curtailing of operations. During the last several years, our strategy has evolved toward partnering with other organizations, specifically Internet Archive, for the long-term backup and maintenance of OSF content. As a result, we no longer describe our preservation approach in terms of a specific number of years.

What does this transition mean for COS’s broader role in open science?

COS’s mission is not changing. This transition focuses OSF’s role while COS continues advancing lifecycle open science through infrastructure, policies, standards and incentives, research and evaluation, and training, guidance, and support for research communities.

It also reflects a more complementary approach to open research infrastructure, with COS and OSF working alongside other services and organizations rather than trying to provide many functions within a single platform.

Why should I continue to use and trust the OSF?

For many people, OSF Projects were the main reason they came to the OSF, and removing active collaboration and storage changes that experience in a fundamental way. We know this decision may also make trust harder, and we cannot expect a statement of reassurance to erase that.

We also recognize that users have experienced technical and usability challenges with the OSF. If we continued with the status quo, we would increase the risk of a dramatic and consequential shutdown of OSF. Reducing the platform’s scope and complexity will allow COS to focus resources more effectively on maintaining and improving the effectiveness and usability of the remaining features. We are making these changes with the purpose of protecting and maintaining the public content that users have shared via the OSF, and to adapt the OSF so that it can be a sustainable and effective part of open science infrastructure.

Going forward, OSF will have a more focused role. Researchers can continue to use it to preregister and document study plans, share Preprints through community-run services, and link those records to related data, materials, code, publications, and other results hosted elsewhere. We understand that preregistration and Preprints are not equally familiar or widely used across all disciplines. COS will continue working with research communities to understand how these practices and OSF’s more focused role can best support their needs.

This Article Is Licensed Under CCO For Maximum Reuse.

Back to Main Support page