Overview
Artifacts enable:- Persistent key-value data storage
- Personal and shared data scopes
- JSON-based structured data
- Cross-session persistence
- Collaborative features
- Interactive AI-powered applications
Artifacts are built directly into Open WebUI, providing a simple storage API that AI models can use to create stateful applications without external databases.
What Are Artifacts?
Artifacts are persistent data objects that survive beyond individual chat conversations. Unlike memories which store context and preferences, artifacts store structured application data. Common use cases:- Journals: Daily logs and note-taking
- Trackers: Habit tracking, goal monitoring
- Leaderboards: Competitive rankings and scores
- Dashboards: Data visualization and metrics
- Collaborative Docs: Shared documents and wikis
- Games: Persistent game state
Data Scopes
Artifacts support two data scopes:Personal Scope
Data accessible only to the individual user:Shared Scope
Data accessible to all users (workspace-wide):Storage Operations
Store Data
Save or update an artifact:Retrieve Data
Get an artifact by key:List Artifacts
Get all artifacts for a scope:Delete Artifact
Remove an artifact:Example Applications
Daily Journal
Journal Application
Journal Application
Habit Tracker
Habit Tracker Application
Habit Tracker Application
Team Leaderboard
Leaderboard Application
Leaderboard Application
Interactive Dashboard
Dashboard Application
Dashboard Application
Best Practices
Data Structure
- Use JSON: Store well-structured JSON data
- Version Your Schema: Include version fields for migrations
- Keep It Small: Store only necessary data
- Index When Needed: Use keys that facilitate lookups
Performance
- Cache Locally: Don’t fetch on every operation
- Batch Updates: Combine multiple changes
- Limit Size: Keep artifacts under 1MB
- Clean Old Data: Implement data retention policies
Security
- Validate Input: Always validate before storing
- Sanitize Output: Clean data before display
- Scope Appropriately: Use personal scope for sensitive data
- Don’t Store Secrets: Never store passwords or API keys
Error Handling
Troubleshooting
Artifact Not Found
- Verify the key is correct
- Check you’re using the right scope (personal vs shared)
- Ensure the artifact was successfully saved
- Confirm you have permission to access the scope
Data Not Persisting
- Check the API response for errors
- Verify JSON data is valid
- Ensure sufficient storage space
- Review application logs
Performance Issues
- Reduce artifact size
- Implement caching
- Limit update frequency
- Archive old data