---
title: "We moved on from Cypress. Why haven't you?"
description: "The best teams are switching to Playwright. Currents is how they run it at scale."
canonical: "https://currents.dev/cypress-to-playwright"
---

# We moved on from Cypress. Why haven't you?

The best teams are switching to Playwright. Currents is how they run it at scale.

- [See why teams switch to Playwright](https://currents.dev/cypress-to-playwright#why)
- [I'm on Playwright, show me Currents](https://currents.dev/)

## On this page

- Why top teams are switching to Playwright
- Case studies
- How to migrate
- Resources

## FAQs

### Do I have to rewrite all my Cypress tests at once?

No, you can migrate your tests gradually. You can even report both Cypress and Playwright tests to Currents, while you haven't fully migrated.

### Can I run Playwright and Cypress side by side?

Absolutely. You are able to set up separate CI workflows to run both Cypress and Playwright tests. You can keep full visibility by reporting both Cypress and Playwright tests to Currents.

### What is Sorry Cypress?

[Sorry Cypress](https://sorry-cypress.dev) is an open-source solution for parallelization and recording of Cypress tests. It is MIT licensed and has been widely used by organizations of all kinds as an alternative to Cypress Dashboard.

Currents was later created as a cost-effective alternative to Cypress Cloud. While we still support Cypress (up to v12), Currents is now fully focused on Playwright

## Ready to join the Playwright side?

See what Currents can do for your Playwright test suite. [Explore Currents](https://currents.dev/).
