Skip to main content
Artifacts in Open WebUI provide a built-in key-value storage API for persistent data. This enables AI models to create and maintain long-lived content such as journals, trackers, leaderboards, collaborative tools, and interactive applications that persist across chat sessions.

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

Habit Tracker

Team Leaderboard

Interactive Dashboard

Best Practices

Data Structure

  1. Use JSON: Store well-structured JSON data
  2. Version Your Schema: Include version fields for migrations
  3. Keep It Small: Store only necessary data
  4. Index When Needed: Use keys that facilitate lookups

Performance

  1. Cache Locally: Don’t fetch on every operation
  2. Batch Updates: Combine multiple changes
  3. Limit Size: Keep artifacts under 1MB
  4. Clean Old Data: Implement data retention policies

Security

  1. Validate Input: Always validate before storing
  2. Sanitize Output: Clean data before display
  3. Scope Appropriately: Use personal scope for sensitive data
  4. 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

Next Steps

  • Learn about Memories for context storage
  • Explore Functions to create artifact-powered tools
  • Build Skills that leverage artifacts