User Guide
Location Library
Build and manage a library of reusable location references for visual consistency
The Location Library is a team-wide collection of location references that can be reused across sequences. It ensures visual consistency when the same setting appears in multiple projects.
Accessing the Location Library
Navigate to Locations from the main navigation. The library shows all locations with a search bar and grid layout.
OpenStory includes a small set of system location templates. Their names and descriptions are displayed in the current interface language and sorted using locale-aware rules. Locations created by your team remain in the language in which they were entered.
Adding Locations
Click Add Location to create a new entry. You can provide:
- Name — The location's display name
- Description — A description of the setting
- Reference image — Upload a photo or AI-generated reference that defines the location's visual style
Searching
Use the search bar at the top to filter locations by name or description. For system templates, search matches both translated text and the canonical English text. The search is reflected in the URL for bookmarking and sharing.
Using Locations in Sequences
Locations can be used in two ways:
Pre-Generation (Suggestions)
When creating a new sequence, click the location icon in the script view's control bar to attach locations as suggestions. The AI will reference their images when generating scenes set in matching environments.
Post-Generation (Updating References)
After generation, go to the Locations tab of your sequence, click a location, and use Update Reference to replace the auto-generated reference with one from your library.
Managing Locations
- Edit — Update the name, description, or reference image
- Upload custom references — Add photos or images that define the location's look
- Search — Filter by name or description
Team Sharing
Locations are scoped to a team rather than stored globally. The current product creates a default team for each account; the underlying role and invitation model supports multiple members, but a complete team-switching and member-management interface is not currently exposed.