Assets FAQs
Create a space to separate brands, websites, or business units that require independent governance. Create a workspace to isolate short-lived work such as campaigns, seasonal updates, or experimentation inside the same space.
Yes. In Contentstack CMS implementations, teams commonly map one or more spaces to a stack (brand or site) and use a shared space (eg., “Global Brand Assets”) for assets reused across stacks through linking.
Yes. When a space is linked to multiple stacks, content teams can reuse assets across stacks through the asset picker, subject to roles, space access, and localization rules.
No. An asset belongs to a single space. To reuse an asset across projects, store it in a shared space (eg., Global Brand Assets) and reference it where needed.
Add languages globally in Assets > Settings first. Then enable only the required languages inside specific workspaces. Only workspace-enabled languages become available for localization in that workspace.
Yes. Add only the required languages at the workspace level. Only those enabled languages become available for localizing assets in that workspace.
Yes. Asset localization can include localized metadata (title/description/tags) and can also include replacing the file when the localized version requires it (eg., an image with translated on-image text).
Unlocalizing removes the localized variant, and the asset starts pulling values again from the default language for that locale.
No. The asset picker respects locale rules. Entries can select assets that match the entry locale or the locale fallback chain, depending on how fallback is configured.
System metadata is generated by Contentstack, is read-only, and tracks file and activity details. User-defined fields are configured through fields and asset types to store business metadata (eg., product ID, usage rights, campaign name).
Yes. Each save creates a new version with asset versioning (eg., updates to file or configurable metadata). Versioning preserves history and enables restoration.
No. The permanent URL remains constant across versions, even when the file is replaced, while version history continues to track changes.
Contentstack supports restoring older versions, but selective deletion of specific versions is not supported as a standard end-user action. Version history exists to support traceability and rollback.
No. Custom version names have a maximum length of 32 characters.
Deleting a workspace deletes the workspace and the assets associated with it. This action is destructive and intended for cleanup of temporary workspaces.
No. Workspace UID is read-only after creation. Create a new workspace if a different UID is required.
Fork creates a new workspace using an existing workspace as the source. Teams commonly fork a campaign workspace to create a new variation without starting from scratch.
Yes. Search and filtering support system fields and user-defined fields. Advanced search supports constructing complex queries across multiple fields.
Yes. Contentstack Assets provides organization/product roles, and each space supports space-scoped roles. Users must be assigned to a space to access its assets, even if a user has a product role.
No. Spaces and workspaces serve different purposes and cannot be converted.
Yes. Assign a Contentstack Assets role and then grant access only to specific spaces.
Yes. Create a custom role (eg., Vendor) with limited permissions and assign it to one or more spaces.
AI features such as tag suggestion, description suggestion, alt text suggestion, visual markup suggestion, and reverse image search depend on asset type and format. Some AI capabilities apply primarily to image formats.
No. Visual markup applies to supported image formats and is not available for non-visual file formats (eg., most documents).
Yes. Asset types can require specific fields and apply validation rules. Assets must meet required-field rules before saving.
Deleted folders/assets can be restored from trash for up to 14 days. After this, the assets or folder and all its contents will be permanently deleted.