Appearance
Saving & Loading Projects
EmberBoard uses two independent save systems to keep your work safe.
Two Save Systems
1. Auto-Save (Browser Storage)
How it works:
- Automatically saves to IndexedDB every 2 seconds
- Happens in the background when you make changes
- No user action needed
- Project auto-restores when you reopen the app
Advantages:
- ✅ Never lose work from crashes or closed tabs
- ✅ Seamless - you don't think about it
- ✅ Instant restore on next visit
Limitations:
- ⚠️ Browser storage has limits (~50-100MB typically)
- ⚠️ Only accessible on this browser/device
- ⚠️ Not shareable with others
- ⚠️ Can be cleared if you clear browser data
- ⚠️ Safari may have stricter limits
WARNING
Auto-save is for convenience, not backups! Always use manual save for important work.
2. Manual Save (Project Files)
How it works:
- File menu → Save Project
- Downloads a
.emberboardfile to your computer - Contains all images and project data in one file
When to use:
- ✅ Create backups of your work
- ✅ Share projects with others
- ✅ Transfer projects between computers
- ✅ Archive finished projects
- ✅ Before making major changes
Best Practice: Save manually at key milestones:
- After completing a major section
- Before trying risky experiments
- End of each work session
- Before sharing for review
Saving Your Project
Save to File
- Click File menu
- Select Save Project
- Choose download location
- File is saved as
ProjectName.emberboard
What's included:
- All beats and their properties
- All images (embedded in file)
- Timeline arrangement
- Settings and preferences
- Project metadata
File size: Depends on number and size of images. Typical projects:
- 10 beats with images: ~5-15MB
- 50 beats with images: ~25-75MB
- Text-only project: <1MB
Loading Projects
Method 1: File Menu
- Click File menu
- Select Open Project
- Choose a
.emberboardfile - Project loads, replacing current project
Method 2: Drag and Drop (Faster)
- Drag a
.emberboardfile from your computer - Drop it anywhere in the EmberBoard window
- Project loads automatically
TIP
Drag and drop works from:
- Windows Explorer / macOS Finder
- Email attachments (save first, then drag)
- Cloud storage (Dropbox, Google Drive, etc.)
Auto-Save Details
When Does Auto-Save Trigger?
Auto-save happens 2 seconds after you:
- Create a beat
- Edit text (title, script, scene heading)
- Add/change an image
- Reorder beats
- Delete a beat
- Change settings
- Modify node colors
Checking Auto-Save Status
Look for the indicator in the top bar:
- Green checkmark - Saved successfully
- Yellow spinner - Saving in progress
- Red warning - Save failed (see troubleshooting)
What's Stored?
Everything in your project:
- Beat content and properties
- Images (as blob URLs in IndexedDB)
- Node positions and colors
- Timeline order
- Project settings
- Undo/redo history (last 50 actions)
Troubleshooting
Auto-Save Failed
Error: "Storage quota exceeded"
Solutions:
- Reduce image sizes (resize before importing)
- Remove unused beats
- Save project file manually and clear browser storage
- Use smaller image formats (WebP instead of PNG)
How to clear browser storage:
- Open browser DevTools (F12)
- Application tab → Storage → Clear site data
- Or use browser settings → Clear browsing data
Project Won't Load
File appears corrupt or won't open
Solutions:
- Check the file isn't damaged (should be valid ZIP format)
- Try opening in a different browser
- Check file size - should be >1KB
- Ensure file extension is
.emberboard
Auto-Save Not Working
Changes aren't persisting
Check:
- Are you in private/incognito mode? (Storage disabled)
- Is browser storage disabled in settings?
- Browser storage full? (Clear cache)
- Third-party cookies blocked? (May affect storage)
Lost My Project
Can't find auto-saved project
Try this:
- Return to the same browser and device
- Open EmberBoard normally - should auto-restore
- Check if you cleared browser data recently
- Try loading a manual save if you created one
Prevention:
- Save manual backups regularly
- Use multiple devices? Save files to cloud storage
- Critical projects? Save at end of each session
Best Practices
The 3-2-1 Backup Rule
For important projects, maintain:
- 3 copies (auto-save + 2 manual saves)
- 2 different locations (computer + cloud)
- 1 off-site (cloud storage)
Naming Convention
Use descriptive names for project files:
- ✅
commercial_storyboard_v3.emberboard - ✅
shortfilm_2025-01-15.emberboard - ❌
project.emberboard - ❌
untitled.emberboard
Version Control
For iterative work:
- Save with version numbers:
v1,v2,v3 - Or use dates:
2025-01-15,2025-01-16 - Keep previous versions until project is final
Example workflow:
my_project_v1.emberboard (initial draft)
my_project_v2.emberboard (after client feedback)
my_project_v3.emberboard (after revisions)
my_project_FINAL.emberboardCollaboration
Sharing projects with team members:
- Save project to file
- Share via:
- Email (if <25MB)
- Cloud storage link (Dropbox, Drive, etc.)
- File transfer service (WeTransfer, etc.)
- Recipient opens in their EmberBoard
- They can edit and send back
WARNING
Only one person can edit at a time. EmberBoard doesn't support real-time collaboration (yet).
Technical Details
File Format
.emberboard files are JSON-based with embedded images:
- Human-readable structure
- Images stored as base64 data URIs
- Compatible with version control (text-based)
- Can be unzipped and inspected
Browser Storage
Uses IndexedDB for auto-save:
- Modern storage API (faster than localStorage)
- Supports large data (>50MB in most browsers)
- Async operations (doesn't block UI)
- Survives browser restarts
Storage Limits by Browser
Approximate limits:
- Chrome/Edge: 60% of available disk space
- Firefox: 50% of free disk space
- Safari: ~1GB hard limit
- Mobile browsers: More restrictive (varies)
Future Features
Planned improvements:
- Cloud sync across devices
- Automatic version history
- Real-time collaboration
- Project templates
- Bulk export/import