Spaces
A space is a flexible content repository for your project. Each space stores distinct stories, blocks, assets, datasources, and configurations (e.g., workflows, users, roles, access tokens).
In your user account, create a new space by navigating to My Spaces > Add Space. Choose a pricing plan or explore a demo and specify a space name. Choose one of the following server locations:
- Europe
- United States
- Canada
- Australia
Storyblok also offers dedicated infrastructure in China.
Selecting an appropriate server location reduces latency for content authors and ensures conformity with privacy and security laws. Learn more about the server location in our API and assets documentation.
Note that the actual content is distributed via Storyblok’s CDN, regardless of the selected space location, ensuring maximum performance.
Settings
Each space has individual settings that you can configure according to your project. Space owners or admins have access to the Settings area, where they can perform space-wide actions, including toggling maintenance mode (to restrict content management to only admins) and permanently deleting your space.
Duplicate a space
In the spaces overview, click on the space options indicated by the three dots in the top right corner. As an admin or owner of a space, use the Duplicate option to open the duplication dialog and provide a name for the copy.
Please note that assets are not copied when duplicating a space. You can copy all assets using the Management API. See this example script for reference.
Multi-space setups
Deciding whether to use one or multiple spaces depends on the specific project requirements and desired architecture. Usual criteria include: team structure, localization requirements, development workflows, and content channels.
Here are some real-world examples to help you make the decision:
| Scenario | Recommendation |
|---|---|
| The development team needs an environment for building and testing components | Use two spaces to maintain independent component schemas |
| The editorial team is working in one region, but some parts of the app need to be translated | There’s no need for separate region-specific spaces. Use field- and folder-level translation to translate content. |
| The company has multiple separate editorial teams in different countries and different languages, each of which has its own content. | Use dedicated spaces for each team to reduce latency and let each team manage workflows, roles, and permissions. If necessary, sync content and component schemas between spaces for efficiency. |
| The mobile team wants to publish content from the website in the mobile app. | Maintain one space for both platforms. |
| A company has three different websites, but the content on the various websites is highly related, with lots of inter-linking and repetition. | Consider using one space with separate folders for each domain. This ensures components can be easily shared. However, This might have some potential drawbacks (for example, editors will need to manually change the preview environment for the required domain). |
To sync content between spaces use either the Management API or the sync operation of the Storyblok CLI. To keep components in sync, you can use the Shared Components app.
Linking between spaces is not supported, To link content between separate spaces, use web links.