# Exporting Stories (/docs/v0-1/story-portal/collaboration/exporting-stories)

## Overview [#overview]

Exporting allows you to download a complete copy of your Living Story as a file. This creates a backup, enables story transfer between systems, or allows you to share stories outside the portal.

## How to Export [#how-to-export]

### Export Process [#export-process]

1. **Open your story** in the Story Portal
2. **Click the Share button** in the top navigation
3. **Click the Export button** at the bottom of the share panel
4. **A file downloads** to your computer automatically

The export process is immediate and doesn't require any configuration or options.

### What Gets Exported [#what-gets-exported]

The exported file includes:
- All scenes and their content
- All sequences and connections
- All interactions and their configurations
- All influences and conditional logic
- Story metadata and settings
- The complete story structure

**Note**: The exact format and structure of the exported file is determined by the backend system.

## Export File [#export-file]

### File Details [#file-details]

- **Automatic naming**: The filename is generated by the system
- **Binary format**: Downloaded as a blob (application/octet-stream)
- **Complete story**: Includes all story data in a single file

### File Location [#file-location]

The file downloads to your browser's default download location (typically your Downloads folder).

## Use Cases [#use-cases]

### Backup and Archive [#backup-and-archive]

**Regular backups**:
- Export before making major changes
- Create milestone backups (v1, v2, etc.)
- Archive completed stories
- Keep local copies of important work

**Backup schedule suggestions**:
- Before granting Edit access to new collaborators
- Before major restructuring
- At project milestones
- Before making a story public

### Story Transfer [#story-transfer]

**When to export for transfer**:
- Moving stories between environments
- Sharing with external collaborators
- Providing stories to clients
- Migrating to a new account (if supported)

### Collaboration [#collaboration]

**Sharing exported files**:
- Send story files via email or file sharing
- Include in project documentation
- Provide to clients for their records
- Share with team members outside the portal

**Note**: Exported files may require import functionality (outside the scope of the share panel) to be opened in another system.

### Documentation [#documentation]

**Documentation purposes**:
- Archive project deliverables
- Include in project files
- Maintain version history manually
- Document story evolution

## Best Practices [#best-practices]

### When to Export [#when-to-export]

**Always export**:
- Before major structural changes
- Before granting Edit access to new users
- Before deleting significant content
- When completing major milestones

**Consider exporting**:
- At the end of each work session
- Before making stories public
- After completing significant features
- When wrapping up a project

### Organization [#organization]

**File management**:
- Create a folder structure for exports
- Include dates in folder names
- Keep milestone versions separate
- Document what each export represents

**Example structure**:
```
My Stories/
  Project Name/
    Exports/
      2024-12-01-initial/
      2024-12-15-v1-complete/
      2024-12-20-before-public/
```

### Version Tracking [#version-tracking]

Since the system doesn't provide built-in version control, use exports for manual versioning:

1. **Name export folders** with dates and versions
2. **Keep notes** about what each version contains
3. **Document major changes** in a separate text file
4. **Archive old versions** you no longer need

**Example version notes**:
```
2024-12-01: Initial story structure with 5 scenes
2024-12-15: Complete first draft, all interactions added
2024-12-20: Final review version before going public
```

### Storage [#storage]

**Storage recommendations**:
- Keep exports in cloud storage (Dropbox, Google Drive, etc.)
- Maintain at least 3 milestone versions
- Delete intermediate exports after major milestones
- Archive completed project exports separately

## Security Considerations [#security-considerations]

### Exported File Security [#exported-file-security]

**Remember**:
- Exported files contain your complete story
- Anyone with the file can potentially view the contents
- Store securely and share carefully
- Don't share exports if story contains sensitive data

**Secure sharing**:
- Use encrypted file sharing when necessary
- Password-protect if sending via email
- Only share with trusted collaborators
- Delete shared files when no longer needed

### Access Control [#access-control]

**Unlike sharing in the portal**:
- Export files have no access control
- No permission levels apply
- No tracking of who has access
- No ability to revoke access

**Use portal sharing when**:
- You need to control who can view/edit
- You want to track access
- You need to revoke access later
- You want ongoing collaboration

**Use export when**:
- You need a permanent backup
- You're delivering final files
- You want offline access
- You need to archive the project

## Limitations [#limitations]

### No Import Functionality [#no-import-functionality]

The share panel only supports **export**. There is no visible import functionality, so:

- Exported files serve primarily as backups
- Re-importing may require backend tools or other interfaces
- Exports are not a direct transfer mechanism (unless import exists elsewhere)

### No Export Options [#no-export-options]

The export is straightforward with no configuration:

- No format selection
- No partial exports (always full story)
- No export settings or preferences
- Automatic filename generation

### No Version Information [#no-version-information]

The export process doesn't include:

- Version numbers in filenames
- Automatic versioning
- Change logs or diff information
- Timestamps in the file itself (only in download time)

**Workaround**: Organize exports manually with dates and version notes as described in Best Practices.

## Comparison with Sharing [#comparison-with-sharing]

### Export vs Make Public [#export-vs-make-public]

| Feature | Export | Make Public |
|---------|--------|-------------|
| Access Control | None | Read-only for public |
| Updates | Static file | Live, updates automatically |
| Tracking | No tracking | Can see access in portal |
| Revoke | Cannot revoke | Can make private again |
| Use Case | Backup, archive | Wide sharing, demonstration |

### Export vs User Sharing [#export-vs-user-sharing]

| Feature | Export | Share with Users |
|---------|--------|------------------|
| Permission Levels | N/A | Preview, View, Edit |
| Updates | Static file | Real-time |
| Collaboration | No | Yes |
| Access Control | None | Full control |
| Use Case | Backup, delivery | Active collaboration |

## Next Steps [#next-steps]

- Learn about [Sharing Stories](/docs/v0-1/story-portal/collaboration/sharing-stories) for active collaboration
- Understand [Managing Access](/docs/v0-1/story-portal/collaboration/managing-access) for permission control
- See [Permission Levels](/docs/v0-1/story-portal/collaboration/permission-levels) for access details