ℹ️ In this article, we refer to the publishing infrastructure used before June 11, 2026 as the "legacy infrastructure," and the current publishing infrastructure as the "new infrastructure."
About Studio.Design's publishing infrastructure
As of June 11, 2026, Studio.Design's publishing infrastructure has been rebuilt so that fully rendered HTML is returned from the server. This makes it easier to see benefits in page loading speed, stability, and SEO.
For projects created on or after June 11, 2026, this new infrastructure is the standard publishing infrastructure.
Projects created before June 11, 2026 will continue to be published on the legacy infrastructure until you switch over. At this time, Studio.Design will not force a switch to the new infrastructure.
New features and improvements going forward will be built for the new infrastructure. We recommend reviewing the differences in specifications and then considering a switch if needed.
💡 For details on how the publishing infrastructure works, see Studio.Design's publishing infrastructure.
💡 If you'd like to improve your published site's loading speed, take a look at these articles as well:
How to switch your publishing infrastructure
Important: What we recommend before switching a live site
Because the legacy and new infrastructures are built differently, differences in specifications or in how you connect external services may affect how your site displays or how analytics are recorded.
If any of the following apply to you, we recommend testing the new infrastructure in a separate test project first, and then switching your live site.
The site is business-critical.
Some pages include tags from external services, such as ad or conversion tracking.
The site gets a lot of traffic, so display and load issues would have a large impact.
Step 1: Check and record how your site looks on the legacy infrastructure
Open the project and review how your currently published site looks.
If needed, record the current state of your site in a separate environment or with screenshots.
Step 2: Switch your publishing infrastructure
Tip: Check your custom domain's A record
Sites with a custom domain whose A record points to the old IP address "35.194.122.208" can't be switched to the new infrastructure.
Before switching, update the A record to point to "34.111.141.225".
In the dashboard of the project, open [Settings].
Select [General] from the menu on the left.
Click the [Settings] button under [Publishing infrastructure].
In the [Change publishing infrastructure] dialog, select the publishing infrastructure you want to use.
Review the description and notes, and if everything looks good, [Save] the setting.
It takes about 5 minutes for the switch to complete after you click [Save].
Step 3: Confirm the switch and generate the cache (first time only)
Confirm that the switch completed correctly, then generate the cache.
Be sure to check using your published site's URL. You can't confirm this in Live Preview.
Point: How cache generation works on the new infrastructure
On the new infrastructure, the HTML for your main pages is prepared in advance at moments such as when you publish or update your site, which helps pages load quickly even on the very first visit.
For details on when the cache is generated and which content is excluded, see Studio.Design's publishing infrastructure > When the cache is generated on the new infrastructure.
Open your published site's URL in a browser and open the browser's developer tools.
In Chrome, you can open the developer tools by right-clicking on the page and selecting [Inspect].
Open the [Elements] tab and search for the keyword "Studio.Design.HRC".
You can search with [Ctrl / Cmd ⌘]+[F].
If you can find
<meta name="generator" content="Studio.Design.HRC">, the switch is complete.Finally, update your site to generate the initial cache.
Tip: Check your settings if you use Google Analytics
If you've connected Google Analytics through Apps, check your enhanced measurement settings after switching.
On the legacy infrastructure, we recommended turning off [Page changes based on browser history events]. On the new infrastructure, you can leave the default settings as they are.
For setup instructions, see Apps: Connecting Google Analytics.
Frequently asked questions about switching and managing your publishing infrastructure
Will sites that are already published switch over automatically?
No. Sites already published on the legacy infrastructure will stay on the legacy infrastructure unless you switch them yourself.
At this stage, Studio.Design won't change your publishing infrastructure for you.
Which infrastructure will newly created projects use?
For newly created projects, the new infrastructure is the standard publishing infrastructure.
Will future features be available on the legacy infrastructure?
New features and improvements going forward will be built for the new infrastructure. In some cases, they may not be supported on the legacy infrastructure.
After switching to the new infrastructure, can I switch back to the legacy infrastructure right away?
You can switch back to the legacy infrastructure until around the end of January 2027. After that, switching back to the legacy infrastructure won't be possible once you've moved to the new infrastructure.
Are there pages or features that are more likely to be affected when switching to the new infrastructure?
Pages that embed external scripts using an Embed box or that include custom code are more likely to be affected. Also, if your setup relies on behavior that's changing on the new infrastructure, pages may not display as you expect.
Review the following details, and pay close attention to whether these pages look and behave the same before and after the switch.
Will switching to the new infrastructure always make my site faster?
In general, you can expect better loading speed and stability than on the legacy infrastructure. However, actual loading speed depends on things like image sizes, external scripts, embedded elements, and page structure. Take a look at the articles below and consider making additional adjustments as well.
Will switching to the new infrastructure always improve my SEO?
Switching to the new infrastructure makes it easier for search engines to read your page content, so your site will be better structured for SEO.
That said, SEO results depend on many other factors, so switching alone won't necessarily improve your rankings. For more details, see our SEO article.
After switching to the new infrastructure, part of my site looks different.
There are some differences in behavior and specifications between the legacy and new infrastructures.