---
title: "Architecture and APIs for integrating JSS Next.js apps with Sitecore editors"
slug: "architecture-and-apis-for-integrating-jss-next-js-apps-with-sitecore-editors"
abstract: "An introduction to integrating editors with JSS Next.js apps, including links to the different methods of doing it. These include using chromes or, if you have JSS 22.1 or later, using metadata."
---
# Architecture and APIs for integrating JSS Next.js apps with Sitecore editors

Prior to the release of JSS 22.1, there was one method of integrating your JSS Next.js apps with Sitecore editors, involving the use of chromes. The 22.1 release added another method of editor integration involving metadata:

- [Metadata](https://doc.sitecore.com/sai/en/developers/jss/22/jss-sai/editor-integration-using-metadata.html "Editor integration using metadata") - the Next.js app is rendered inside an iframe within SitecoreAI Pages. It offers several advantages over the chromes method, including faster load times, simplified architecture and configuration, the ability to [connect your local host to Pages](https://doc.sitecore.com/xmc/en/developers/xm-cloud/en/connect-your-local-host-to-pages.html) without using a tunnel, and avoiding the need to manage the editing data cache. This method is supported by SitecoreAI Pages only.
- [Chromes](https://doc.sitecore.com/sai/en/developers/jss/22/jss-sai/editor-integration-using-chromes.html "Editor integration using chromes") - the data is sent using a `POST` request to the Next.js `/api/editing/render` endpoint, and the resulting page markup is sent back to the editor. This method is supported by both Sitecore Experience Editor and SitecoreAI Pages.

> [!important]
> If you're using JSS 22.1 or later and SitecoreAI Pages, we recommend you choose the metadata method. If you don't need to integrate with Sitecore Experience Editor, you can also [make some configuration changes](https://doc.sitecore.com/sai/en/developers/jss/22/jss-sai/optimize-performance-for-metadata-based-integration.html "Optimize performance for metadata-based integration") to further optimize your editor integration.