Quick Answer: The DeepSeek chat demo is an open-source static web app that calls the DeepSeek API straight from your browser, with no application backend. Install Node.js 22.12+ and pnpm, run
pnpm dev, or double-click a downloadedindex.html. Then enter your API key in Settings before your first chat.
Most chat wrappers route your prompts through someone else's server. The deepseek chat demo, published by deepseek-ai on GitHub, does the opposite. Its README states that no application backend is required, so your browser talks directly to the configured API service. That changes where your key lives, where your conversations sit, and what you need to deploy it. Here's what actually matters before you run it.
What "no backend" actually means for you
A static app is just HTML, CSS, and JavaScript. Nothing runs on a server you control, so every request comes from the browser tab itself. That's the appeal: there's no middleman logging your prompts.
It also means the trust boundary moves. Your API key and settings are stored in the browser's localStorage. Conversations and original attachments go into IndexedDB. The README is explicit that sending messages, uploading attachments, and using speech features sends that content to the API service you configured.
Here's the counter-intuitive part. Static does not mean private. The app keeps data off a server you run, but the API provider still receives everything you send. Treat the chat box like a third-party API client, not a local notebook.
Three ways to run it, and when each one fits
There are four realistic entry points. Pick based on whether you want to hack on the code or just chat.
- Use the hosted demo. Open the online app, enter your key, and go. Fastest, but you depend on the hosted copy.
- Use a release archive. Download the archive from the Releases page, extract it, and double-click
index.html. No installation or build step. - Run the dev server. Install Node.js 22.12+ and pnpm, then run
git clone,pnpm install, andpnpm dev. Open http://localhost:8090. - Build and host it yourself. Run
pnpm build, then deploy thedist/folder to any static web server.
| Method | Install needed | Best for | Main caveat |
|---|---|---|---|
| Hosted demo | None | Quick trials | You rely on someone else's copy |
| Release archive | None | Personal use, offline-ish setup | file:// storage and CORS limits |
pnpm dev | Node.js 22.12+, pnpm | Development and testing | Runs only while the dev server is up |
pnpm build + static host | Node.js 22.12+, pnpm, a web host | Team or family access | Your host now serves the page to others |
Here's where most people get tripped up. The README says you can open index.html directly, but it adds a condition: your browser must support storage on file:// pages, and the API service must permit those cross-origin requests. If chats fail to save or the first message errors out, that condition is usually the reason. Running pnpm dev removes the guesswork because the page loads from a real origin.
Setting up your API key and model
Open Settings and enter your key in the API key field before you send anything. The key lives in localStorage on that origin, which is why you'll need to re-enter it if you switch browsers or clear site data.
The default chat model is deepseek-flash, reached through Anthropic-compatible Messages and Files APIs. The README also says requests include extensions for search, link reading, titles, and latest_reminder. That's a meaningful detail. A plain OpenAI-style gateway that handles basic chat may not support those extensions, so features like smart search or link reading can fail even when basic messages work.
The API origin is set in rspack.config.ts, which defaults to https://api.deepseek.com. You can override it with createConfig({ apiOrigin, devServer }). Use that if you're routing through a proxy, but test every feature you care about, not just a single message.
Your data: where it lives and how to move it
Think of the app as having two storage layers, and it helps to know which is which.
- localStorage: API key, settings, and preferences.
- IndexedDB: conversations, branches, and original attachments.
Both are isolated by browser profile and site origin. That isolation explains the most common support question. If your chat history seems to vanish, you probably opened the app in a different browser profile, a different browser, or a different origin, such as switching from localhost:8090 to a hosted URL. Your data didn't disappear. It's in another bucket.
Export is useful for backups. Settings uses ZIP archives, and the chat history export ZIP includes conversations and locally available original images. It excludes your API key, settings, and original non-image attachments. So a restored archive won't bring back your key or your PDFs.
Import is the part most people misread. After confirmation and validation, importing replaces all local conversations and attachments. It doesn't merge. If you import an old archive on a device with new chats, the new chats are gone. Export first.
"Delete all chats" is a separate action. It clears local conversations, original attachments, and unsent drafts, stops any ongoing reply, and keeps your API key and settings. It doesn't delete files already uploaded to the API service, so you'll need to handle those through your provider.
Failure modes that catch experienced developers
Two problems show up repeatedly, and neither is obvious from the UI.
First, the attachment picker is not a format guarantee. The README says supported formats are determined by server-side validation. A file can upload cleanly, look fine in the chat, and still be rejected or processed unexpectedly. Test one file of each type you need before you rely on it.
Second, the repository naming is inconsistent. The clone instructions use chat-demo, while the releases link points to deepseek-chat-demo. The name difference may just be a redirect, but verify the URL before you download an archive, especially on a machine that handles sensitive keys. Check the release is published by the expected organization.
Voice input carries its own caveat. Speech features send audio to the configured ASR and TTS endpoints. If you're dictating anything sensitive, that's a disclosure question, not just a UX choice.
Trade-offs: is a self-hosted static client worth it?
Here's the honest comparison. A static client gives you control over the interface, the storage model, and the deployment target. You can read the source, pin a version, and run it offline from a folder. You also take on responsibility the vendor would normally carry, including key handling and browser security.
Key handling deserves the most thought. An API key stored in localStorage can be read by any script running on that origin, and by anyone with access to your unlocked browser profile. For a personal machine, that risk is usually acceptable. For a shared deployment, the safer pattern is a small server-side proxy that holds the key, which is exactly the architecture this project avoids. Choose the setup that matches who else can reach the browser.
For a single user who wants a clean, inspectable chat client, the trade-off favors this project. For a team that needs central key management or audit logs, it doesn't.
Frequently Asked Questions
What is the DeepSeek chat demo?
The DeepSeek chat demo is an open-source static web app from deepseek-ai that connects directly to the DeepSeek API from your browser. It has no application backend. It supports multiple conversations, streaming replies, attachments, Markdown and math rendering, and history import and export. Your API key is stored in localStorage on the browser.
How do I run the DeepSeek chat demo locally?
Install Node.js 22.12+ and pnpm, clone the repository, run pnpm install, then run pnpm dev. Open http://localhost:8090 and enter your API key in Settings. Alternatively, download a release archive, extract it, and open index.html directly, provided your browser supports storage on file:// pages.
Why does my chat history disappear?
Conversations are stored in IndexedDB, which is isolated by browser profile and site origin. Opening the app in a different browser, a different profile, or a different URL, such as localhost versus a hosted domain, uses a separate storage bucket. Your data is usually still there. Export a ZIP backup regularly to avoid losing it.
Does the export include my API key?
No. The ZIP export includes conversations and locally available original images, but excludes API keys, settings, and original non-image attachments. Re-enter your key after restoring an archive on a new browser or device.
Can I use it without a build step?
Yes. Download the release archive, extract it, and double-click index.html. No installation or build is needed. Some features may behave differently on file:// pages because of browser storage rules and the API service's cross-origin policy, so test your key and a sample message first.
Run the release archive this week, enter your key, send one message, then export a ZIP and check what it leaves out. Pass this to a colleague who keeps asking why their chats vanished, because the answer is almost always the browser profile.