Adobe Commerce · Frontend
Adobe Commerce PWA Studio — official headless frontend
PWA Studio is Adobe's framework for building headless storefronts on Adobe Commerce (formerly Magento) with React and GraphQL. It is still maintained: Adobe released version 14.5.1 in May 2026. What changed is the landscape around it: Hyvä has been free since November 2025, and Adobe offers its own storefront on Edge Delivery Services. At WolfSellers we implement PWA Studio when it is the best option, support stores already running it, and help teams decide whether to stay or migrate.
Definition
What is PWA Studio?
PWA Studio (Progressive Web App Studio) is the set of tools, libraries and starter code Adobe distributes to build Progressive Web Apps connected to Adobe Commerce through GraphQL. It is not a theme or a plugin: it is a complete React application, maintained by Adobe with community contributions, that replaces the classic frontend (Luma or Blank).
Compared with the classic frontend, it offers a service worker (caching and offline mode), push notifications, install-to-home-screen and an app-like experience. In exchange it demands more technical complexity, extra SEO work and a team experienced in React.
Status
Is PWA Studio still current?
Yes. Adobe keeps shipping releases in the official PWA Studio repository on GitHub: 14.3.0 in July 2025, 14.4.0 in October 2025, 14.5.0 in February 2026 and 14.5.1 in May 2026 (verified on September 21, 2026). It has not been discontinued, despite articles that declare it over.
What changed is the context. Adobe offers its own storefront on Edge Delivery Services, with ready-made components for cart, checkout and account, and Hyvä, the theme that competes with PWA Studio in most projects, has been free and open source since November 2025. Today PWA Studio is one option among several, not the default path.
Decision
PWA Studio vs Hyvä, Edge Delivery Services and Luma
These are the real options today, seen from the perspective of someone evaluating PWA Studio. The full comparison, including custom headless frontends, is on our Frontend & UX service page.
- PWA Studio: a fit if you need to share UI with a React mobile app, real PWA features (install, offline mode, push) or already have a senior React team and an investment in this stack.
- Hyvä: replaces Luma without leaving the Adobe Commerce stack (PHP, Alpine.js and Tailwind). It is the most direct option for most stores and, since November 2025, the theme carries no license cost.
- Adobe's storefront on Edge Delivery Services: the natural path if you run Adobe Commerce as a Cloud Service or Adobe Commerce Optimizer. On PaaS it requires Adobe Commerce 2.4.8 or later plus Adobe's catalog services.
- Luma: the default theme, supported and familiar, but heavy and hard to bring to good Core Web Vitals.
Stores on PWA Studio
If your store already runs PWA Studio: maintain, optimize or migrate
A store on PWA Studio doesn't need to migrate just because other options exist. These signals help decide:
- Maintain and upgrade: the store is stable, the team knows React, and upgrades to the 14.x releases keep pace with your Adobe Commerce upgrades.
- Optimize: the site works, but Core Web Vitals or SEO fall short. This is usually solved with prerendering of key pages, code splitting and lighter GraphQL queries.
- Migrate: the team no longer has React skills, every change costs too much, or you are moving to Adobe Commerce as a Cloud Service, where Edge Delivery Services is the native path.
Capabilities
What comes in PWA Studio
PWA Studio is a framework with ready-made components and patterns:
- Venia: reference storefront with home, product listing, product page, cart, checkout and account
- Peregrine: React hooks library for data, form state and GraphQL
- Buildpack: build system with a webpack configuration optimized for Adobe Commerce
- UPWARD: the server that sits between the storefront and Adobe Commerce, delivers the initial HTML and proxies requests (UPWARD-JS and UPWARD-PHP implementations)
- GraphQL connection to catalog, customers and orders
- Service worker: caching strategies, offline mode and background sync
- Extensibility framework: extensions (the equivalent of Adobe Commerce modules) to customize without touching the core
Performance
Well-implemented PWA Studio performance
PWA Studio can perform excellently or poorly depending on how it's implemented. The UPWARD server delivers the initial HTML with the application shell and meta tags from the server; the rest of the page renders in the browser. Top-performing projects have:
- Prerendering or server-side rendering of key pages for SEO: home, categories and product pages
- Aggressive route-based code splitting and dynamic imports for heavy components
- Image optimization with Adobe Dynamic Media or similar, never the original file
- Optimized GraphQL queries: only the fields needed, plus persisted queries
- Service worker with cache-first for static assets and network-first for the API
- Smart preloading of the most likely next routes
- Core Web Vitals as KPIs: LCP under 2.5 s, CLS under 0.1 and INP under 200 ms
Delivery
What we do with PWA Studio
We work on PWA Studio on three fronts: new projects when it is the right choice, support for stores already running it, and planned migrations. A new enterprise project takes 5 to 9 months, longer than an equivalent Hyvä build.
- Technical discovery: validate whether PWA Studio, Hyvä or Edge Delivery Services is the right choice for your case
- Upgrades to the latest PWA Studio releases, aligned with your Adobe Commerce upgrades
- Performance and SEO audit: Core Web Vitals, initial HTML, bundle size and GraphQL queries
- Frontend architecture: monorepo with a UI kit shared between web and mobile app (React Native)
- Component library in Storybook to govern the UI
- GraphQL integration with Adobe Commerce: Live Search, Page Builder and B2B
- Planned migration to Hyvä or Edge Delivery Services, protecting SEO
- Client team training in React, GraphQL and extensibility
Frequently asked questions
What is PWA Studio?
Has PWA Studio been discontinued?
PWA Studio or Hyvä: which should I choose?
What is Adobe's storefront on Edge Delivery Services?
Does PWA Studio have good SEO?
How much does a PWA Studio project cost?
Related services
Frontend & UX
High-performance Adobe Commerce frontend and UX: Hyvä, Adobe's Edge Delivery Services storefront or headless, with measured Core Web Vitals.
Learn more →Composable Commerce
Composable / MACH architecture on Adobe Commerce: API-first, headless, best-of-breed. Implementation with PWA Studio, decoupled frontend and microservices.
Learn more →Adobe Commerce
Adobe Commerce (formerly Magento) implementation with all native capabilities: catalog, checkout, payments, promotions, Page Builder and more.
Learn more →Custom software development
Custom modules, microservices, APIs and extensions for Adobe Commerce or standalone stacks — built in 2-week Scrum sprints with working deliverables.
Learn more →Want to discuss your project?
We'll assess your case at no cost and propose a concrete path forward.
Tell us about your project
No field is required. Just leave us a way to reach you.