ChromaDB UI is a web app for exploring and managing a ChromaDB instance through a visual interface instead of raw API calls.
Important
ChromaDB UI only works with the Chroma v2 API
You can try the deployed UI here:
- Connect to a ChromaDB server with a URL, tenant, and database.
- Browse all collections in the current workspace.
- Create, rename, clone and delete collections.
- Inspect and edit collection metadata.
- Run semantic text search inside a collection.
- Choose an embedding provider for semantic queries, including OpenAI or Ollama.
- Run embedding-based nearest-neighbor search with raw vector JSON.
- Search records in the current collection.
- Build metadata filters for the current table view.
- Select multiple rows and run bulk actions like delete, metadata patch, and selected-row CSV export.
- Add records with IDs, documents and metadata, then either paste embeddings manually or auto-generate them from document text.
- Import or upsert JSON records with explicit embeddings or auto-generate missing embeddings from document text.
- Collection metrics viewer with document, metadata, sampled embedding stats, and quality audit findings.
- Review a recent activity log inside the current workspace.
- Edit documents, metadata, and embeddings.
- Open a full vector viewer for large embeddings.
- Export the current table view as CSV.
You can use ChromaDB UI in three ways:
- Run it locally with
npm run dev. - Run the app in a Docker container with Docker Compose.
- Try it out on the deployed GitHub page.
Follow these steps if you want the local Vite workflow.
- Clone the repository.
git clone https://github.com/BlackyDrum/chromadb-ui.git- Install dependencies.
npm ci- Start the development server.
npm run devThe app runs on http://localhost:8090 by default.
This repository includes a docker-compose.yml file, so you can start only ChromaDB, only the UI container, or both together.
- Ensure Docker is installed and running on your machine.
- Use the command that matches the workflow you want.
Only ChromaDB:
docker compose up -d chromadbOnly the UI container:
docker compose up -d --build chromadb-uiChromaDB and the UI together:
docker compose up -d --buildThe UI container serves the production build at http://localhost:8090.
If you encounter CORS errors while running the application, you'll need to ensure that the Chroma backend allows requests from the correct frontend origin.
persist_path: "/data"
cors_allow_origins: [
"http://localhost:8090", # For local development
"https://blackydrum.github.io", # For the deployed GitHub Pages app
]After making these changes, restart the containers or local dev server.
If you are using the deployed GitHub Pages app and want to use Ollama for record creation or semantic query search, you need to add an environment variable for Ollama:
OLLAMA_ORIGINS=https://blackydrum.github.ioAfter making these changes, restart Ollama.




