Shift with red gradient lettering

Upgrade Tailwind 1.x to Tailwind 2.x

The Tailwind 2.x Shift automates the upgrade of your project from Tailwind 1.x to Tailwind 2.x. This includes all of the changes listed in the Tailwind Upgrade Guide.

This includes upgrading your Tailwind configuration file, replacing utility class references, adopting the new color palette, and much more.

Using the Tailwind 2.x Shift to automatically upgrade your project has an estimated time savings of 4 hours.

Screenshot of a pull request with automated changes from the Tailwind 2.x Shift

Watch a demo


  • Running Tailwind 1.x (configurable for any project).
  • Running Node.js 12.13 or higher.

Core Upgrades

The Tailwind 2.x Shift automates many of the upgrades listed in the Tailwind Upgrade Guide, including:

  • Bumping package.json for Tailwind 2.x.
  • Adding PostCSS and autoprefixer dependencies.
  • Updating the tailwindcss/typography and tailwindcss/forms plugins.
  • Removing instances of old Tailwind utility classes.
  • Converting old Tailwind utility classes.
  • Enabling new Tailwind 2.x variants.
  • Changing Tailwind configuration option key names.
  • Adding leading utilities to responsive text elements.
  • Modernizing @apply statements.
  • Stripping theme() array dereferences.
  • Prefixing keyframe animations.
  • Converting screens to new variants.

Additional Upgrades

In addition to the Core Upgrades, the Tailwind 2.x Shift automates optional upgrades listed in the Tailwind Upgrade Guide, including:

Manual Upgrades

There are some upgrades the Tailwind 2.x Shift can not perform automatically. When Shift detects these it adds a detailed comment to the Pull Request to guide any additional steps you may need to do manually.

In addition, if you are using Tailwind UI within your project, you may also run the Tailwind UI Shift to complete the upgrade to Tailwind 2.x.

Custom Configuration

By default, Shift will look for the Tailwind config file to determine your project path. This will be used as the base path when searching for additional assets and templates.

When not specified, Shift will assume a Laravel project structure. If you are not using a Tailwind configuration file or have a different project structure, you may configure Shift for your project.

Sign in with any of the following services to connect Shift with your Laravel project.

Don't use one of these services?

Temporarily push your project to a free, private repository on one of these cloud-based services or upgrade your project locally with Shift for Docker.