Recommended Free Tools
Magento PWA Studio is Adobe’s set of developer tools and libraries for building a Progressive Web App (PWA) storefront that connects to Adobe Commerce or Magento Open Source. The storefront is a separate frontend application. It does not reuse a Magento theme’s layout files, theme assets, or scripts. Instead, it requests product, cart, and account data from the commerce backend through GraphQL and REST services.
Installing PWA Studio does not turn an existing Magento theme into a PWA, and it does not improve performance on its own. What it gives you is a local starter storefront you can run, customize, and eventually deploy. This guide explains what the pieces are, how to get a first project running, and which production route applies to your environment.
As an Amazon Associate I earn from qualifying purchases.
What PWA Studio is and what it is not
PWA Studio is a toolkit. Adobe describes it as a collection of tools and libraries for setting up a development environment and building storefront components and extensions. It is not a hosted storefront you can sign up for. You build the frontend, host it, and keep it connected to a commerce backend you already run.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →The separation matters most in practice. A traditional Magento theme is tied to the commerce application’s rendering pipeline. A PWA storefront owns the presentation layer, so frontend developers can work on it without changing the backend’s theme files, and the two sides communicate only through the backend’s APIs. The trade-off is that the storefront still depends on the backend for catalog data, cart logic, checkout, and customer accounts.
#1 Best Overall
The architecture and the package roles
Adobe’s architecture documentation divides the project into packages. Knowing their roles makes the rest of the setup easier to follow.
| Package or component | Role in a PWA Studio project |
|---|---|
| Buildpack | Build and project configuration tools, including the commands used to scaffold and run the project |
| Venia UI | Rendering components for the storefront interface |
| Peregrine | Hooks and logic that components use for behavior |
| Venia Concept | A starter storefront that you can customize rather than build from nothing |
Packages are versioned independently, so a Venia UI release and a Buildpack release do not necessarily move together. Check the release notes for the versions you install.
Requirements before you start
Adobe’s prerequisites page lists familiarity with React, Node.js 18 or later, and either Yarn (recommended) or npm. The page also says Yarn v2 is not supported.
The same page is inconsistent about Node versions. In one place it states a minimum of Node.js 18 or later. In another, it says PWA Studio supports Node LTS versions, “currently v16 and v18.” Those statements do not agree. Before you install, open the prerequisites page for the release you plan to use and confirm which Node version it names. If you are starting a new project, pick the Node version that release’s documentation states explicitly.
Windows is not supported for development because of dependency incompatibilities. Adobe’s FAQ lists Docker and Windows Subsystem for Linux (WSL) as community workarounds, not officially supported paths.
Build a first local project
Adobe’s setup tutorial scaffolds a storefront based on Venia. The commands below are the ones the tutorial uses. Command names and prompts can change between releases, so compare them with the tutorial for your version.
-
Create the project. Run the scaffold command in an empty working directory:
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.yarn create @magento/pwaThe tool asks setup questions, such as the backend connection details, and creates the minimum files for the Venia storefront. The tutorial’s example project folder is
pwa-studio-fundamentals. -
Enter the project folder.
cd pwa-studio-fundamentals -
Create a custom local origin. The tutorial uses a custom hostname and SSL certificate so that the local site runs over HTTPS:
yarn buildpack create-custom-origin ./HTTPS matters because service workers and push notifications require a secure context in the documented local setup. A plain
http://localhostaddress will not exercise those features the same way. -
Start the development server.
yarn watchOpen the origin the tool reports in a browser and accept the local certificate. If the page loads but shows no products, move to the backend connection checks below.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Connect the storefront to the backend
The storefront needs a reachable Adobe Commerce or Magento Open Source instance with GraphQL and REST services enabled. Most first-run problems come from this connection, not from the frontend build.
If catalog or other Magento data does not appear, check these items in order:
-
The backend URL in
.env. Confirm that the development server can reach the address set inMAGENTO_BACKEND_URL. A URL that works in your browser may still fail from the development server if it sits behind a network restriction or a different hostname. -
Store-view configuration. Adobe’s FAQ notes that choosing a store view can require store-code configuration on the backend. If the storefront loads for the default view but not for another, compare the store codes in the backend with those the frontend requests.
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.Rank #4
-
Backend version. Compatibility depends on the Commerce or Open Source version and the PWA Studio release. Adobe’s deployment guidance tells you to verify this pairing before you deploy.
Choose a production route
Production setup depends on where the storefront will run. Adobe documents two main routes, and they are not interchangeable.
| Question | UPWARD-JS (Node server) | UPWARD-PHP (Adobe Commerce Cloud) |
|---|---|---|
| Where it fits | A generic host that supports Node.js processes | Adobe Commerce Cloud, which does not support Node processes for serving the storefront on this route |
| Build step | yarn build produces the production build |
Build output is produced through the Cloud deployment process |
| Serving the app | yarn start runs the production UPWARD-JS server |
Served through the Magento UPWARD connector and UPWARD-PHP |
| Key settings named by Adobe | NODE_ENV, MAGENTO_BACKEND_URL, CHECKOUT_BRAINTREE_TOKEN |
Commerce modules, environment variables, and deployment steps described in the Cloud tutorial; exact values are not stated in this guide |
On a generic Node-capable host, Adobe’s production checklist covers environment variables, the production build, and the server start. Confirm that your host runs the Node version the release requires before you build.
On Adobe Commerce Cloud, follow the Cloud tutorial rather than the generic checklist. It covers verifying compatibility between your Commerce instance and the PWA Studio version, configuring the Magento UPWARD connector, and the deployment steps. Re-read Adobe’s current Cloud documentation before you deploy, because deployment specifics change between releases.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Payments and what you still have to build
Venia includes Braintree payments out of the box. Other payment methods are not part of the starter and need additional storefront implementation. Plan that work before you promise a checkout flow to a client or stakeholder.
Customization also has a language boundary. Adobe’s external tools guide says JavaScript is the primary language of the project and is necessary for working with PWA Studio in your own projects. It adds that PHP may be needed for heavier backend customization. In practice, a PWA project is a JavaScript and React project that talks to a PHP-based commerce backend.
“JavaScript is the primary language used in the PWA Studio project, and knowing how to develop with it is necessary for using PWA Studio in your own projects.”
Adobe, PWA Studio developer documentation (external tools and libraries guide)
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesSpecial offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
What a PWA adds, and what it does not guarantee
Adobe’s overview describes the features typically associated with PWAs: HTTPS, responsive design, browser compatibility, offline caching, installation on mobile devices, and shareable URLs. These are properties of the PWA approach. A freshly scaffolded Venia project shows them only once your configuration, caching strategy, and hosting meet the requirements. Scaffolding the project does not by itself deliver offline support or a speed gain.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
