Gemini Gems Not Saving: Protect Your Instructions First

When a Gemini Gem fails to save, the first thing to do is copy your instruction text out of the editor before closing the tab. A failed save can sometimes result in an empty instructions field if you return to the Gem later, and the text in the editor may be the only copy you have. Once the text is safe, you can work through the common causes.

Tools like fenbs keep a permanent copy of tested instructions as Skills, so a failed save in Gemini does not mean starting over. See the Gemini Gems overview for background on how Gems store their instructions.

Copy your instructions before anything else

Select all the text in the instructions field and copy it to a document, a note app, or a Skills entry in fenbs. Do this before refreshing the page, before trying a different browser, and before any other step. A page refresh may clear an unsaved draft.

Once the text is in a safe place, you can try to save again without the risk of losing your work. This also gives you a copy to paste back in if the save succeeds but the field appears empty when you return.

Common reasons a Gem fails to save

Most save failures fall into a small number of categories. Work through them in order.

• Session expired: a long editing session can time out your Google login. The save button may appear to work but the change is not recorded. Sign out and sign back in, then paste your copied instructions and try again.
• Network drop: a brief connection interruption during the save shows a generic error or no response. Check your connection and retry.
• Character limit reached: Gem instructions have a limit on how much text they accept. If you are near or over it, the save will fail. Check Google's Gemini help center↗ (opens in a new tab) for the current limit. Shorten the instructions and try again.
• Browser extension interference: extensions that modify page behavior can block form submissions. Disable extensions and try saving in a private window.
• Stale page: if the Gems editor has been open for a long time without interaction, the page may have lost its connection to the server. Reload and paste your copied instructions back in.

How to check which edits actually persisted

After a save attempt, do not trust the editor view alone. Close the Gem and reopen it, or navigate away and come back. If the changes you made are visible in the instructions field after reopening, the save worked. If the field shows older text or is empty, the save failed.

Check this on a fresh page load, not the same tab you were editing in. A cached view can show the unsaved version while the server has a different one.

Recovering from a failed save

If the save failed and you do not have a copy of the instructions, you can sometimes find an older version in the Gem. Open the Gem and check what instructions it has. If it has a previous working version, you can work from that as a starting point and add your recent changes.

If the Gem is completely empty, you will need to write the instructions again. The Gemini Gems templates guide has a set of starting templates for common tasks that can speed up rebuilding.

Preventing save loss in future

The safest habit is to write and test instructions in a document or note before opening the Gems editor. Then paste the finished text in, confirm it saves, and close the tab. Writing directly in the Gems editor is convenient but means the text exists only there until the save succeeds.

For the Claude Projects vs Gemini Gems comparison and more on managing instructions across tools, see the ai-prompts topic hub.

What to do when the Gem appears blank after a save

Sometimes a save succeeds but the instructions field appears empty when you return to the Gem. This can happen if the interface loads a stale cached version. Reload the page with a hard refresh (Shift+F5 or Ctrl+Shift+R on most browsers) before concluding the save failed.

If the field is still empty after a hard refresh, check on a different device or in a private window. A blank field in one browser that shows the correct instructions in another confirms a local caching problem, not a save failure. Clearing the browser cache for gemini.google.com should resolve it.

If the field is empty everywhere, the save did not persist. Paste your copied instructions back in, sign out and sign in again to refresh the session, and save again. If saves continue to fail, try a different browser. If the problem persists across browsers and devices, contact Google support through the Gemini interface.

How to do this with fenbs

1. Create a free account and open your personal kanban board.
2. Open Skills and prompts. Add a Skill for each Gem instruction you have tested and want to keep.
3. When you edit a Gem in the future, paste the updated text into the Skill as well so both copies stay in sync.
4. If a save fails in Gemini, the text is already in fenbs. Copy it from there and paste it back into the Gem editor.
5. Connect a supported AI app via Integrations so it can read the same instructions without needing Gemini at all.