What Are Gems in Gemini? A Practical Guide

What a Gem is, and the test for when to build one

Gems tend to get built once, shared in a team chat with a cheerful message, and quietly stop being used a few weeks later. The usual cause is not the Gem. It was a task that didn’t repeat, or instructions nobody maintained, or a file that went stale while everyone assumed it was current.

A Gem is a saved, customized version of Gemini. Google’s help page describes it as something you create and save to shape Gemini’s responses to a specific need.^[1] In practice that means a name, written instructions and optional reference files, kept so a chat starts with them already loaded.

A marketing manager who pastes the same two paragraphs of brand voice into every new chat is the clearest case for one. The paragraphs stay the same, the task comes back every week, and only the draft varies. That is what a Gem is for.

There is a second thing to know before you build anything. As of October 19, 2026, Google says Gems are being replaced by skills in the Gemini app, starting with personal accounts in November 2026, with the details and sources further down. I checked every Google page below on that date, so you can judge how old this is. The advice still holds, but it changes how I’d build.

Gem or prompt: three questions that settle it

The choice between a Gem and a one-off prompt comes down to three questions. Three yes answers and a Gem earns its place. Fewer, and you’re maintaining something a prompt would have done as well.

Here is how that sorts some ordinary marketing work. Recurring jobs pass because the structure and the reference stay put while the input changes: the weekly campaign recap, a brand-voice check, a screen of agency pitches against your brief. A brainstorm of names, one awkward email or a single long report fail, and the brainstorm fails for a particular reason: locked-in instructions work against the variety you want from it.

The case people argue about is meeting notes turned into an action list. A Gem with no files is just saved instructions, and a text file holding your prompt does almost the same job. The Gem pulls ahead when other people need to run it the same way, or the reference material is bulky.

Writing the instructions, with a filled-in example

Google’s help page describes four areas for Gem instructions: a persona, a task, context and a format, and says you don’t need all four.^[2] I’d treat the task and the format as non-negotiable and the persona as optional. The context is where the value tends to sit, because it’s the part you used to paste into every chat.

Below is a worked example, written as the instruction text itself, for the weekly campaign recap. It’s my illustration, with a fifth block of limits. I haven’t run it against a live account, so test it on your own data first.

Two habits improve it. Google’s page says you can write a sentence or two about your goal and use the Use Gemini to re-write instructions option to expand it, then review and edit before saving. That’s a fair start from a blank page if you read what comes back. The second habit is keeping the master copy of the instructions in a document you control, which I’ll come back to.

Knowledge files give the Gem its reference material. Google’s page says you can upload files from your device, add files from Google Drive or add a NotebookLM notebook, and that Drive files need Keep Activity on and Google Workspace connected to Gemini Apps. It also says Gemini uses the latest version of a Drive file, so edits show up in the Gem. That cuts both ways: a current file is a feature, and one edited by accident is a problem in every run.

Plans, limits and what Google doesn't say

Here is what I could and couldn’t confirm about plans and limits on October 19, 2026.

• Personal accounts. You need to be signed in to Gemini Apps and 13 or over, or the applicable age in your country. The page lists no subscription tier, so I won’t add one.
• Work or school accounts. These may be subject to different terms, and the admin page on Gem sharing names no Workspace editions. Ask your administrator rather than guessing from a plan name.
• Knowledge file limits. The Gems page states no file count or size limit, and Google’s general upload page says nothing specific about Gems, so test your own files.^[3]
• Where Gems work. Not with Gemini Live. Web-made Gems appear in the mobile app and the Workspace side panel.

One distinction trips people up. Google also has a separate product, Gems from Google Labs, which builds small apps from a description, needs a personal account and an age of 18 or over, and can’t be created from classic Gems.^[4] Everything else in this guide is about classic Gems, the saved-instructions kind.

Sharing a Gem: who sees what

Sharing is where a Gem stops being a personal shortcut and becomes something a team depends on, and where privacy mistakes happen.

Google’s sharing page describes two levels. A viewer can use the Gem and also view its instructions and uploaded files. An editor can do all of that, change the instructions and files, share it further and delete it.^[5] The page spells out that anyone with access can see the instructions and files, and advises against sharing a Gem with anyone who shouldn’t see those files.

A team lead shares a Gem built for performance reviews, and a colleague opens it to check the output. The colleague can also read the instructions, including the line about how to handle one person’s review, and the reference file under it.

A few more details are worth knowing before you click Share:

• Shared Gems live in Google Drive, so Gems with uploaded files can be shared only if those are device files or Drive files. A NotebookLM notebook can’t be the source.
• You can set an expiry on someone’s access and choose general access from Public, Anyone with the link, Your organization or Private.
• Removing someone’s access removes the Gem from their Drive. A Gem shared with you doesn’t appear in your list until you open and use it.

For work accounts, the organization decides. Google’s admin page says an administrator can turn Gem sharing on or off for everyone or chosen groups, and that shared Gems follow Drive’s sharing rules, so if Drive allows external sharing, Gems can be shared outside the organization too. Turning the setting off stops sharing in the app but doesn’t remove access that already exists.^[6] That last point is why the checklist below includes a look at who already has access.

Test it before the team does

Before a Gem goes to a team, it should pass a short test. This is the version I’d use, and it takes about as long as running the Gem a few times.

The fifth check is the one people skip, and it matters for trust. A Gem that can say “I can’t tell” is safer than one that answers whatever it is given, because a polished wrong answer reads exactly like a polished right one. The reasons are the ones behind why AI hallucinates. Run the checklist again whenever the instructions or files change, not only before the first share.

Gems are becoming skills: what to do about it now

This is the section that changes what I’d build. Google’s transition page says that starting in November 2026, Gems will transition to skills in Gemini Apps for personal Google Accounts, with Gems for Workspace business, enterprise and non-profit accounts removed in March 2027 and education accounts in June 2027.^[7] Google’s Workspace admin page gives those as no sooner than March 1 and June 1, 2027, and says that from November 17, 2026 Gems move to Settings in the Gemini app, where they can still be created, edited and used.^[8] The September 30 announcement says skills will soon replace Gems for tailoring instructions to specific tasks.^[9]

A skill, per Google’s help page, is a set of reusable instructions and additional context that you pick with a slash or that Gemini can apply when it seems relevant.^[10] Existing Gems will be recreated automatically as skills, and Gems by Google Labs will not migrate.

The Workspace side reads a little differently from the personal one. The admin page says migrated Gems arrive as inactive drafts that creators must review and activate before use or sharing, with Drive permissions carried over, while the personal-account page says sharing isn’t available for skills yet. I’d read that as a sequencing difference, and I’d check the live pages before promising anyone a date.

What does that mean in practice? A Gem’s value is the instructions and the reference files, not the container. Automatic conversion is reassuring, but a conversion you haven’t checked is one you’re trusting. I’d rather you owned the text.

How Gems compare to GPTs, Projects and agents

People ask whether a Gem is the same as a custom GPT, a Claude Project or a Copilot agent. I wouldn’t call them equivalent, and the vendors’ own pages don’t either. They share a purpose: each keeps instructions and reference material together so you don’t rebuild them every chat. After that they diverge on sharing, actions and who can build one.

Anthropic describes Projects as self-contained workspaces with their own chat histories and knowledge bases.^[11] OpenAI’s page says new GPT creation isn’t available on personal ChatGPT accounts and that it plans to retire custom GPTs.^[12] Microsoft tells agent builders to record licensing requirements first.^[13] Containers keep changing, which is a reason not to build your workflow around one.

If you’re choosing between assistants for work, the ChatGPT, Claude and Gemini comparison covers that decision. If you already have a custom GPT, our custom GPT guide is the same idea in another tool, and the same advice about owning the text applies.

Work accounts versus personal accounts: what you can load

Work and personal accounts handle your data differently, and a Gem tends to hold things you’d rather keep private: a brief, a policy, a style guide with a client’s name in it.

For personal accounts, Google’s privacy page says a subset of chats is reviewed by human reviewers and that your activity is used to develop and improve Google services. It advises you not to enter confidential information you wouldn’t want a reviewer to see, and it lists the instructions you give in Gems and skills among the information Gemini Apps collects.^[14] For work or school accounts, Google says editions with enterprise-grade protections don’t have chats and uploaded files reviewed by human reviewers or used to improve models, while editions where Gemini is an additional service are treated differently.^[15] Your administrator can tell you which applies, and it’s the first question to ask before anyone uploads a file.

Since everyone you share a Gem with can read all of it, a Gem built on sensitive material should have a narrow audience even where the account allows loading it. The table below is my own working rule, a judgment and not Google’s.

If you’re unsure where a file falls, check before you load it.

Who owns what, by role, and how to tell it's working

Delegation needs spelling out, because a Gem that works well can quietly move decisions to the wrong place.

If your Gems already exist, this prompt turns one into a portable master copy. Paste your current instructions in and keep what comes back in your own document.

For a team, the master copies go in a register, with one row per Gem, the master copy’s location and a status column you update when your account’s date arrives.

The first Gem differs by seat.

Measuring whether it works takes more than counting who opened it.

A small team can start with one Gem and a reminder. Structured training from an experienced facilitator shortens the learning curve and builds shared capability across a team, because people practice writing instructions for their own work. In our terms, training builds the capability, the Gem is the workflow design that gives it somewhere to be used, and the quarterly review is the reinforcement that turns it into behavior. Our guide to training employees on Gemini covers the sequence: build the basic habit first, then role-specific tools like Gems.

Your first week

Start with one task and keep it small. Here is a week that needs no budget, only a few agreements.

For step 4, this prompt writes your bad inputs for you.

Before you share anything, delete what you’d be uncomfortable seeing forwarded. Then find your account’s transition date and put it in the register. For where notebooks fit, see notebooks in Gemini, and for the side-panel features Gems appear in, the Workspace upgrade guide.

Hina Mian, Co-Founder of Future Factors AI

Hina is a marketing strategist with over a decade of hands-on campaign experience across B2B and consumer brands. She writes about using AI to run leaner, sharper marketing without losing the human touch. Future Factors helps professionals and teams build practical AI capability through role-based training, workflow design, and hands-on adoption.

More about Hina →