Supabase UI Library
shadcn registry of blocks that wire a UI straight into Supabase auth, storage and realtime
Supabase's own shadcn-compatible registry (the site now resolves to supabase.com/library). It ships 12 distinct blocks — Supabase client, password auth, social auth, dropzone upload, realtime cursor, realtime chat, realtime avatar stack, realtime Monaco, realtime flow, current-user avatar, infinite query and the Platform Kit — each published per framework, for 60 registry items in total. Every block is real wiring, not just markup: the auth block includes routes, middleware and server clients. Frameworks covered are Next.js, React, React Router, TanStack Start, Vue and Nuxt.
npx shadcn@latest add https://supabase.com/ui/r/realtime-chat-nextjs.jsonUse this the moment a project already has Supabase — it saves you writing the auth route handlers, cookie-aware server client and RLS-safe upload paths by hand, and the generated code lands in your repo so you can edit it. Always append the framework suffix to the registry item name (realtime-chat-nextjs vs realtime-chat-tanstack); picking the wrong one silently pulls the wrong client. It assumes shadcn/ui is already initialised, and the realtime blocks need Realtime enabled on the project, so check both before you promise the user a working chat.
Why it is here. First-party registry from the backend vendor itself, so the blocks track Supabase API changes instead of drifting the way third-party auth starters do.
- first-party Supabase blocks
- 60 registry items across 6 frameworks
- realtime cursors, chat and presence out of the box
- Platform Kit for embedding Supabase management UI
- ships companion AI skills
Verified 2026-08-15. HTTP 200. https://supabase.com/ui (redirects to https://supabase.com/library), https://supabase.com/ui/r/registry.json (full 60-item manifest), https://supabase.com/ui/docs/getting-started/quickstart, https://supabase.com/ui/r/realtime-chat-nextjs.json (200), GitHub API repos/supabase/supabase
