Ask AI with the files that matter, then inspect the diff.
Reference local source files, get a proposed change, and keep the final write behind an explicit review step.
Chrome extension for web AI work
Stop copy-pasting your project into web AI.
ChatFile brings local files, pages, and AI answers into one browser workspace. Send only the right context to ChatGPT, Claude, Gemini, and more, then capture useful output and review every file write before it touches disk.
Built for Chrome and Chromium browsers with side panels and local folder access.
Local-first indexes stay in your browser
Works with ChatGPT, Claude, Gemini
Review first no silent local writes
Works beside the AI tools you already use
ChatGPT
Claude
Gemini
DeepSeek
Kimi
Qwen
Sharper everyday workflows
Built for the moment web AI needs your actual files.
ChatFile is for people who already use browser AI, but keep losing time moving project context, research, and AI output by hand.
Turn pages and answers into project notes instead of loose tabs.
Capture useful web AI responses or current pages as Markdown and CSV drafts that can become reusable context.
Keep good answers searchable across future chats.
Save durable workflow outputs into the local workspace so later prompts can start with context instead of archaeology.
The missing layer in web AI
Stop moving work between folders, tabs, and chats by hand.
ChatFile turns the messy loop of copying snippets, chasing previous answers, and applying edits manually into one reviewable workflow.
Copy, trim, paste, repeat.
Manually open files, guess which snippets matter, paste huge blocks into a chat, then move useful answers back by hand.
Reference, capture, review.
Add local files as context, capture web answers into drafts, and approve write proposals before local files update.
Why it feels different
A real project workspace next to your web AI tab.
Instead of dumping giant prompts into a chat, ChatFile lets you choose context, keep useful answers, and approve local file changes with clear boundaries.
01 - Reference
Insert local files without paste walls.
Add a folder, pick the files that matter, and send compact file chips to the current AI chat.
- Browse local folders from the side panel.
- Search indexes before sending a prompt.
- Keep prompts shorter and easier to review.
02 - Capture
Turn good web AI answers into local drafts.
Save selected answers, current pages, Markdown notes, or CSV drafts before they disappear inside a long conversation.
- Capture answers as reusable context.
- Convert pages to Markdown or table drafts.
- Keep follow-up work in the project workflow.
03 - Review
See the diff before anything writes to disk.
AI-generated edits become write proposals with paths, warnings, and explicit allow or reject controls.
- Review file paths and diffs first.
- Approve only the changes you trust.
- Keep local files under your control.
01
Add project
Authorize a local folder through Chrome.
02
Find context
Search files, pages, and reusable snippets.
03
Send to AI
Insert clean context into the current chat.
04
Review output
Capture answers and approve writes.
Clear plan boundaries
Start free, upgrade when the workflow becomes durable.
Free is enough to try the core loop. Pro is for larger context, multi-source work, history, schedules, and saving outputs back into the local workspace.
Single-project trial loop
- Connect 1 local project.
- Send up to 3 files or snippets per context package.
- Use up to 200KB of ChatFile context.
- Preview current-page and single-source workflows.
Bigger context and saved workflows
- Send up to 20 files or snippets per context package.
- Use up to 1MB of ChatFile context.
- Unlock multi-source, tab groups, schedules, and history.
- Create reviewed write proposals for local project saves.
ChatFile is the workspace layer, not a model subscription.
ChatFile Pro does not include third-party AI memberships, model subscriptions, or API credits. Use supported web AI sessions or your configured providers.
Chrome Web Store story
Five install reasons, each with one job to do.
Less paste, better context, durable answers, reviewed writes, and clear local data boundaries.
Local-first by design
Your local workspace stays under your control.
Project indexes, folder handles, drafts, settings, and write proposals live in browser-local extension storage. Selected snippets or page text are sent only when a workflow needs them.
Folder handles, file indexes, settings, and write proposals stay in extension storage.
File snippets, page text, or selected answers are sent only after you run that action.
Every local file change is prepared as a proposal and needs approval before saving.
Trust before install
Know what ChatFile can access before you add it to Chrome.
The extension asks for browser capabilities because it lives next to web AI pages and local files. These are the practical boundaries.
Does ChatFile upload my whole project?
No. Local indexes, folder handles, drafts, settings, and write proposals stay in browser-local extension storage. Selected snippets move only when you run a workflow that needs them.
When does data leave my browser?
When you send chosen file context to a web AI page, call a configured API provider, use a remote embedding provider, sign in, or complete payment. The target service handles that content under its own terms.
Why does the extension need tab and scripting permissions?
ChatFile uses them to detect supported AI inputs, insert chosen context, capture selected answers, read user-selected tabs, and keep the side panel coordinated with the current page.
Can AI write to my files without approval?
No. AI output becomes an editable draft or write proposal first. A local file is written only after you review the path, warnings, and diff, then approve the save.
What should I use for screenshots and demos?
Use a throwaway folder with fictional files only. Do not record private documents, real customer data, personal paths, or identifiable account details.
What happens when I uninstall ChatFile?
Chrome removes the extension's local storage for that browser profile. Your original local files are not deleted.
Ready for Chrome
Bring project context into the AI tabs you already use.
Start with one local folder, send the right context, capture the useful answer, and review file changes before they happen.