
Shopify Oxygen is the hosting platform for Hydrogen storefronts, included at no extra charge on paid Shopify plans. It runs your storefront code as a Web Worker on Cloudflare's open-source workerd runtime and manages environments, deployments and rollbacks for you. It does not make a store fast on its own: speed on Oxygen comes from caching Storefront API data and suitable pages on purpose, keeping customer data out of shared caches, and controlling what the browser has to download.
- Oxygen is free on paid Shopify plans and hosts Hydrogen's React Router starter; Next.js goes to Vercel.
- In Hydrogen 2026-10, a Storefront API query is only cached if you give it a strategy.
- Full-page caching serves whole pages without running your code, but never for cart or account pages.
- Each deployment starts with a cold page cache, so ship outside traffic peaks.
What Shopify Oxygen is in 2026
Oxygen is where Shopify hosts headless storefronts built with Hydrogen. You create a storefront under Sales channels, Hydrogen in the Shopify admin, connect a GitHub repository or deploy from the command line, and Oxygen takes care of servers, scaling and certificates. A few facts shape everything else:
| What it means | |
|---|---|
| Runtime | Your storefront runs as a Web Worker on Cloudflare's open-source workerd runtime, not as a Node server |
| Code | Web-standard APIs (fetch, Web Streams, Web Crypto); Node-only APIs such as Buffer, the file system and process.env are not available |
| Price | Included on paid plans: Starter, Basic, Grow, Advanced, Plus and Pause and build; not offered on Agentic plans |
| Frameworks | Hosts Hydrogen's React Router starter; since Hydrogen 2026-10, the Next.js starter deploys to Vercel instead |
| Before launch | Shopify asks you to pass its Hydrogen production checklist against a production build |
Choosing between Oxygen and Vercel, and whether to go headless at all, is covered in Shopify Hydrogen in 2026. This guide assumes your storefront runs on Oxygen and focuses on running it well.
How a request is served
When a shopper opens a page, the request reaches an Oxygen data center near them. If a valid cached copy of the page exists, Oxygen returns it without running your code. If not, your Worker runs: it calls the Storefront API and any other services, each call either answered from cache or fetched fresh, and streams the HTML back. The browser then downloads the JavaScript, CSS and images the page needs. Every speed problem on Oxygen sits in one of those steps, so every fix below targets one of them.
Environments and deployments
Every Hydrogen storefront has a production environment linked to your default branch and a preview environment for other branches, and you can add custom environments tied to their own branches. Environments are private by default: only people logged in to the store can view them.
| Plan | Public environments |
|---|---|
| Starter, Basic, Grow, Advanced | 1 |
| Shopify Plus | 25 |
| Pause and build | 1 |
| Development stores and trials | 0 |
Deployments are immutable snapshots of your code and environment variables. Each gets its own preview URL, you can roll an environment back to an earlier deployment without rebuilding, runtime logs are kept for a month, and deployments stay available for at least six months, with the ten most recent per environment always kept. Two consequences matter for speed and stability:
- Change a variable, redeploy. Existing deployments keep the old value until you deploy again.
- Do not judge speed on a private URL. Oxygen checks authentication on every request to a private environment, so it loads more slowly than the public site. Test performance on a public environment.
Caching: the biggest lever on Oxygen
Most slow Oxygen storefronts are slow because the Worker waits on data it could have reused. There are two layers to set up.
1. Cache Storefront API queries. Hydrogen's storefront client caches a query only when you give it a strategy. The presets:
| Strategy | Fresh for | Then served stale while refreshing | Use for |
|---|---|---|---|
| Long | 1 hour | 23 hours | Menus, collections, pages, product content |
| Short | 1 second | 9 seconds | Data that changes often but can be briefly stale |
| None | Not cached | Not cached | Cart, customer and other personalized data |
Mutations are never cached, and Customer Account API data is never cached. Third-party data such as reviews or CMS content needs its own cache rule. Each Oxygen data center keeps its own cache, so a page that is warm in one region can still be cold in another.
2. Cache whole pages where it is safe. Oxygen can store the response your Worker generates and serve it to later visitors without running the Worker at all. In Shopify's full-page cache documentation, written for legacy Hydrogen, a response is cached when it carries an Oxygen-Cache-Control header with public and a non-zero max-age, plus a Vary header such as Accept-Encoding, Accept-Language. Only GET responses with 2XX or 3XX status are cached, and any response that sets a cookie is not.
| Good candidates for full-page cache | Never cache publicly |
|---|---|
| Homepage | Cart and cart drawer data |
| Collection pages without personalization | Account, login and order pages |
| Campaign landing pages | Pages that show prices or content per customer |
| Content and policy pages | Any route that sets a cookie |
Stale-while-revalidate lets a cached page refresh in the background, so shoppers rarely wait on a fresh render. Shopify also notes that you cannot purge the cache of the current deployment and that a new deployment does not reuse cached responses from the previous one: every release starts cold. Schedule deployments outside traffic peaks and freeze code before events like Black Friday, as the Black Friday preparation guide recommends.
After the response: assets and scripts
Oxygen's job ends when the HTML leaves the data center. Everything the browser must then download and run is yours to control: ship less JavaScript by rendering non-interactive parts on the server and splitting code by route, serve responsive modern-format images without lazy-loading the main product image, and remove or delay analytics, chat and review scripts that do not help the purchase. Deloitte found a 0.1-second faster mobile site lifted retail conversions by 8.4%.
Measure what shoppers experience
Track Core Web Vitals from real visitors by template and device: Largest Contentful Paint of 2.5 seconds or less, Interaction to Next Paint of 200 milliseconds or less and Cumulative Layout Shift of 0.1 or less are rated good. Add server response time by country, since caches are regional. Then rank fixes by revenue: the best-selling product pages, paid traffic landing pages and the cart first. Review these numbers every month and after every release that adds an app, script or integration, because headless storefronts slow down one addition at a time. Keep the Shopify conversion tracking checks in the same routine so a faster release never ships with broken analytics.
How Glued helps Oxygen storefronts
Glued audits Shopify storefronts, headless or theme, for the speed, UX and checkout problems that cost orders, then designs, builds and measures the fixes as part of a conversion program. For Oxygen stores that means mapping slow routes to revenue, reviewing cache rules and scripts with your developers, and testing changes against conversion rate rather than a lab score. Start with a free audit or see how ongoing optimizations work.
The bottom line
Oxygen removes the hosting work from a Hydrogen storefront and costs nothing extra on paid plans, but it only serves what you tell it to cache. Give every Storefront API query a strategy, cache safe pages whole, keep customer data out of shared caches, deploy outside peaks and keep the browser's workload small. For the wider program, see Shopify optimization services.
FAQ
What is Shopify Oxygen?
Oxygen is Shopify's hosting platform for Hydrogen storefronts. It runs your storefront as a Web Worker on Cloudflare's open-source workerd runtime, with environments, deployments, rollbacks and runtime logs managed from the Hydrogen sales channel in the Shopify admin.
Is Shopify Oxygen free?
Yes. Oxygen is included at no extra charge on paid Shopify plans: Starter, Basic, Grow, Advanced, Plus and Pause and build. Shopify does not offer it on Agentic plans. What a Hydrogen store costs is the development and maintenance of the custom storefront.
Do I have to host Hydrogen on Oxygen?
No. Since Hydrogen 2026-10, your framework decides where you deploy. Shopify's React Router starter deploys to Oxygen, and its Next.js starter, Vercel Shop, deploys to Vercel.
Is Oxygen built on Cloudflare?
Oxygen runs storefronts on workerd, Cloudflare's open-source Workers runtime. That is why storefront code must use web-standard APIs such as fetch and Web Streams rather than Node-only APIs such as Buffer or the file system.
How do I cache pages on Oxygen?
There are two layers. Cache Storefront API queries by giving each one a strategy, such as a long cache for menus and collections. For whole pages, Shopify's full-page cache documentation sets an Oxygen-Cache-Control header with public and a max-age on the response, plus a Vary header. Never cache pages with cart or customer data.
Does a new deployment clear the Oxygen cache?
Effectively, yes. Shopify notes that Oxygen won't serve a cached response from a previous deployment on a new one, so each release starts with an empty full-page cache. Avoid deploying during traffic peaks.
Get A Free Website Audit.
We’ll identify what’s leaking revenue on your site and show you how to fix it. The free audit includes: