You spent 15 minutes building a custom Gem — instructions, knowledge files, sample prompts — hit save, and it’s gone, greyed out, throws Sorry, we can't save your gem., or reopens with empty fields. A very common variant: the Gem saves fine but your uploaded knowledge files “disappear” the next time you chat with it.
The fastest fix for that disappearing-knowledge case: you almost certainly attached files inside a chat (temporary) instead of adding them to the Gem’s Knowledge section and clicking Update. Files added in a chat live only in that one conversation. Re-add them under the Gem’s Knowledge area and save the Gem itself.
For an outright save failure, it’s usually one of: a stale browser session, a special character or over-length field that the editor rejects, a knowledge file that failed to upload, a browser extension blocking the save call, or — on a work account — a Workspace admin policy. Important update: as of June 2026 Gems are free for anyone with a Google account (creation is web-only, at gemini.google.com). So a missing paid plan is no longer the usual cause for personal accounts — that gate was removed in 2025.
Which bucket are you in
| Symptom | Most likely cause | Jump to |
|---|---|---|
| Files vanish on next chat, but the Gem exists | Files attached in chat, not in the Gem’s Knowledge; or you skipped Update | Step 1 |
Sorry, we can't save your gem. on every save | Stale session, special characters, or over-length field | Steps 2-4 |
Error: 1107 when updating an existing Gem | Edit conflict / stale record; recreate the Gem | Step 5 |
| Save works in incognito, not your main browser | Cached session or a blocking extension | Steps 2-3 |
| Save fails only with a file attached | Knowledge file upload failed (size/type/network) | Step 4 |
| Work (Workspace) account can’t save; personal can | Admin policy or propagation delay | Step 6 |
Common causes, by frequency
1. Knowledge files attached to a chat, not the Gem (very common)
There are two different places files can go, and they behave differently:
- Gem Knowledge (permanent): added in the Gem editor under Knowledge, saved with Save/Update. Available in every future chat with that Gem.
- Chat attachment (temporary): the paperclip inside a single conversation. Gone when that chat ends.
If your Gem “forgets” documents or hallucinates instead of citing them, the files were almost certainly chat attachments. They were never part of the Gem.
How to tell: open the Gem editor (pencil icon) and look at the Knowledge section. If it’s empty, the files never saved to the Gem.
2. Stale browser session
If you recently changed accounts or a Workspace admin just changed your access, your client session can lag the actual entitlement, and writes silently fail or hit the wrong endpoint.
How to tell: an incognito window saves the Gem fine; your normal profile doesn’t.
3. A special character or over-length field
Community reports as of June 2026 are clear that certain inputs trip the save: very long instructions, pasted content with unusual unicode/control characters, or smart-quote-laden markdown. The editor returns a generic Sorry, we can't save your gem. with no field highlight.
How to tell: save succeeds with a one-line instruction like You are a helpful assistant., then fails again when you paste your full instructions back in.
4. Knowledge-file upload failed silently
A Gem accepts up to 10 knowledge files (as of June 2026). If one file errors out — over the per-file size limit (around 100 MB), an unsupported type, or a dropped connection — the whole Gem save can roll back with no visible error.
How to tell: removing all knowledge files lets the Gem save; adding them one at a time pinpoints the bad file.
5. Browser extension interfering
Aggressive privacy extensions (uBlock Origin with strict lists, Privacy Badger, Ghostery) and some VPN extensions that strip cookies can block Gemini’s save endpoint.
How to tell: disabling extensions (or using a clean incognito profile) makes saving work.
6. Workspace admin policy or propagation delay
On a work account, an admin can disable Gemini features for your org unit, and a freshly flipped setting can take up to 24 hours to reach you.
How to tell: your personal Google account saves Gems but your work account can’t, and IT recently changed Gemini access.
Shortest path to fix
Gems are created and edited on the web only — gemini.google.com on a desktop. You cannot create or edit a Gem in the Android or iOS app, only run existing ones. If you’ve been trying to save from mobile, switch to a computer first.
Step 1: Put knowledge files in the Gem, then click Save/Update
- On gemini.google.com, open the left sidebar and click Explore Gems (or Gems).
- Click the pencil/Edit icon on your Gem (or New Gem to start fresh).
- Under Knowledge, click Add files and upload from your device or Google Drive.
- Click Save (new Gem) or Update (existing Gem). The blue button is the actual commit — closing the editor without it discards everything.
If files keep “disappearing” between chats, this is almost always the fix: they were chat attachments, not Gem knowledge.
Step 2: Hard refresh and sign out / in
Cmd/Ctrl + Shift + R on gemini.google.com
If that fails:
Profile icon -> Sign out
Close the browser fully
Reopen, sign in, retry SaveThis forces a fresh session token that picks up your current account state. Do a full sign-out, not just a tab refresh.
Step 3: Try an incognito window (isolates cache + extensions)
Open an incognito / private window, sign in, and recreate the Gem. If it saves there:
- Clear cache for
gemini.google.comonly: ChromeSettings -> Privacy and security -> Cookies and site data -> See all site data and permissions, searchgemini, delete its data. - Disable extensions one at a time, starting with ad blockers and privacy tools.
Step 4: Isolate a special character or a bad knowledge file
If you get Sorry, we can't save your gem. even in incognito with no extensions:
- Replace your instructions with one plain line (
You are a helpful assistant.) and save. If that works, the problem is in your instruction text. - Paste your real instructions back in halves to find the offending block. Common culprits: very long instructions, exotic unicode, or smart quotes from a word processor — retype or paste as plain text.
- Save with zero knowledge files. If that works, add files one at a time, saving between each, until one breaks the save. Keep each file under the size limit (around 100 MB) and to a supported type (PDF, DOCX, TXT, common formats); a Gem holds at most 10 files.
Step 5: Recreate the Gem (fixes Error: 1107 and corrupted records)
If a specific Gem throws Error: 1107 on update, won’t open, or repeatedly fails to save, the server-side record is likely stale or conflicted:
- Copy its instructions and note the knowledge files.
- Delete the broken Gem from Explore Gems.
- Create a New Gem with the same content.
- Add knowledge files one at a time, saving between each.
Editing the same Gem from two tabs or devices at once also triggers conflicts — close the duplicates first.
Step 6: For Workspace accounts, confirm admin access
Have your admin verify in the Admin Console at Generative AI -> Gemini for Workspace (the path was reorganized in early 2026; Gemini settings now live under Generative AI) that Gemini and Gems are enabled for your organizational unit. After they confirm, wait up to 24 hours before retesting — Workspace changes are not instant. Note: some consumer-style features may be restricted on certain Business tiers for compliance reasons.
Step 7: Try a different browser entirely
If incognito in Chrome also fails, switch engines (Chrome to Firefox, Edge to Safari). Some save failures come down to one browser’s storage layer hitting a quota or a corrupted cookie. Firefox often surfaces errors Chrome silently swallows.
Step 8: File a ticket if all else fails
If you’re on the web, no extensions interfere, incognito fails, a second browser fails, your instructions are short and plain, and recreate doesn’t work, it’s a real bug. Report it in the Gemini Apps Community or via in-app feedback with: account email, Gem name, the exact error (Sorry, we can't save your gem. or Error: 1107), browser version, a screenshot of the save attempt, and the Network-tab response for the failing save request (DevTools -> Network -> click the failing request -> Response).
How to confirm it’s fixed
- Save the Gem, then fully reload
gemini.google.com(do not just navigate back). - Reopen the Gem in the editor — your instructions and all knowledge files should still be there under Knowledge.
- Start a brand-new chat with the Gem and ask it something that requires a knowledge file (for example, “What does my uploaded doc say about X?”). If it cites the file instead of guessing, the knowledge is truly persisted, not just a chat attachment.
Prevention
- Treat the first save with instructions only as a smoke test. If that won’t save, adding files won’t help — fix the instruction field first.
- Add knowledge files one at a time, saving between each, so a bad file is obvious immediately.
- Always click the blue Save/Update button before leaving the editor; closing the panel does not save.
- Keep a copy of each Gem’s instructions in a Doc (Drive, Notion) so a lost Gem isn’t a lost workflow; date-stamp versions so you can see what changed after a Google update.
- Paste instructions as plain text to avoid smart quotes and stray control characters that can block the save.
- After any account or plan change, sign out and back in before editing a Gem — never trust the cached session.
- Don’t edit the same Gem from two tabs, devices, or browsers at once; last-write-wins can wipe a careful edit.
- For Workspace, confirm IT has Gems enabled for your OU before you invest time building.
FAQ
Do I need Gemini Advanced or AI Pro to create Gems? No. As of June 2026, anyone with a free Google account can create and use custom Gems on the web. Paid tiers (Google AI Pro / Ultra, Workspace Gemini) raise usage limits and add the in-app Workspace side panel, but they are not required to save a Gem.
Why do my uploaded files disappear when I start a new chat? They were attached to a single chat, not added to the Gem. Open the Gem editor, add the files under Knowledge, and click Update. Files added in the Knowledge section persist across every chat with that Gem; chat attachments do not.
I keep getting “Sorry, we can’t save your gem.” What now? Save with one plain line of instructions and no files. If that works, add your real instructions back in halves to find a bad character or over-length block, then re-add files one at a time. If even the minimal Gem won’t save, it’s a session/extension issue — try incognito and a full sign-out.
Can I create a Gem on my phone? No. Gem creation and editing are web-only on a desktop browser at gemini.google.com. The mobile apps can run existing Gems but can’t create or edit them.
What’s the limit on knowledge files in a Gem? Up to 10 files per Gem as of June 2026, each up to roughly 100 MB and a supported type. If a save fails only with files attached, one of them likely exceeds a limit or failed to upload.