Summary: Google is turning off Opal, its Labs experiment for building AI mini-apps, on November 17, 2026, together with "Gems made by Labs" in Gemini. Your workflow files stay in Google Drive under My Drive > Opal, but they will stop running, and they will not be converted for you. This guide shows what to save before the deadline, how to rebuild an Opal workflow as a skill in Gemini or a prompt in Google AI Studio, and where the two replacements fall short.
Everything below was checked on Google's own pages today: the Opal FAQ on developers.google.com, the notice on opal.google, and the Gemini Apps Help articles about skills and the Gems-to-skills transition. I did not have Opal workflows of my own to migrate for this post, so the steps are taken from the official help pages rather than from a hands-on migration log. Where Google's pages are silent (for example, the exact hour on November 17 when the service stops), I say so instead of guessing.
What is actually shutting down, and when
The Opal FAQ, under "Why is Opal ("Gems made by Labs") graduating, and where can I build next?", says the experimental Opal service at opal.google.com and "Gems made by Labs" in Gemini will turn off on November 17, 2026. The banner on the opal.google landing page repeats the date and adds that active workflows will no longer run after it. Google describes this as a "graduation": what the team learned from Opal fed into skills in Gemini, which Google calls its newest core feature for saving and reusing custom instructions in chat.
Three separate things change on that date, and it helps to keep them apart:
- Opal mini-apps (built at opal.google or as "My Gems from Labs" in the Gemini web app) stop running. The files remain in your Drive.
- Classic Gems on personal accounts for people 18 or over become read-only on November 17, 2026 and are removed from Gemini Apps on December 17, 2026. Unlike Opal, these are converted to skills automatically.
- The open-source code: the Breadboard and Opal ADK repositories on GitHub (breadboard-ai/breadboard and breadboard-ai/opal-adk) move to read-only, archived mode. They stay public under their licenses, so you can still clone or fork them, but hosted endpoints such as breadboard-ai.web.app turn off alongside opal.google.com.
Work and school accounts follow a later Gems timeline (March 2027 for Workspace business, enterprise and non-profit accounts; June 2027 for education), but that schedule is for Gems. The Opal FAQ gives a single date for Opal itself.
The one sentence most people will miss
The FAQ is blunt: "Existing Opal workflows will not automatically migrate, so you'll need to set up any new skills or prompts manually." If you read headlines about Gems turning into skills automatically, that applies to classic Gems, not to Opal mini-apps or Gems from Labs. Nothing is lost from Drive, but nobody is going to rebuild your workflow for you.
Step 1: Back up your Opal workflows before November 17
Copy prompts while the editor still works
Google's own recommendation for the period before November 17 is to open each workflow on opal.google.com and copy any prompts or custom instructions you want to keep. Do this now, while you can still see the graph. A practical routine for each mini-app:
- Open the workflow in the Opal editor (the FAQ notes the editor view is optimized for a desktop computer).
- Go through the steps in order and paste each prompt into a plain text document. Note what each step takes as input and what it produces, because that ordering is the part you will have to rebuild by hand.
- Write down which steps used tools such as web search, and which produced images, video or audio. Those are the steps that will need the most rethinking later.
- Run the app once with a typical input and save the output. A known-good example makes it much easier to check whether the rebuilt version behaves the same.
Download the files from My Drive > Opal
The FAQ says your saved workflow files live in your personal Google Drive in a folder called "Opal" (My Drive > Opal), and that Google will not delete or touch them when the service turns off. Even so, a local copy costs nothing. Google Drive Help describes the standard download: go to drive.google.com, click a file, Ctrl-click (Windows) or Command-click (Mac) any others, then right-click and choose Download.
Reading the files after the shutdown
After November 17 you can still get your prompt text by downloading the workflow files from that Drive folder and opening them in any plain text editor, such as Notepad or TextEdit. That is the official fallback. It means the prompts survive, but the clickable app does not. Expect to read raw text rather than a tidy step-by-step view, which is another reason to make your own clean notes before the deadline.
If you shared an Opal
The FAQ explains that sharing an Opal also shares the underlying Drive file. Once workflows no longer run, a shared link stops being a working app, so tell anyone who relies on one of your mini-apps where its replacement will live. If you shared with editor view enabled, remember that those people can see your prompts through the Drive file; review sharing on that folder if any prompts are sensitive.
Step 2: Choose where each workflow should go
Google points to two destinations. Skills in Gemini are meant for everyday tasks and customized chat prompts. Google AI Studio is meant for deeper prototyping and custom prompt experiments. A rough rule from the help pages: if your mini-app was mostly "follow these instructions with this reference material", it maps well to a skill. If it chained several model calls, generated media, or you want to turn it into a real app, AI Studio and the Gemini API are the closer fit.
| Option | Cost / free access | Limits verified today | Good for |
|---|---|---|---|
| Opal (until Nov 17, 2026) | No price is listed in the Opal FAQ | Stops running on Nov 17, 2026; files stay in My Drive > Opal; no automatic migration | Chaining text, image and video prompts with tools like web search into mini-apps |
| Skills in Gemini | Available without a Google AI subscription | Must be 18+ and signed in; up to 100 MB of files per skill; unlimited skills but only 100 active at once; scripts can't make internet requests; doesn't yet work with Canvas, Deep Research, Create video or Create music | Reusable instructions plus reference files, called with / (or @) in any chat or picked up automatically |
| Google AI Studio (Gemini API) | Free tier with free input and output tokens; paid tier for production | Free tier has limited access to certain models and content is used to improve Google's products; paid tier adds higher rate limits, context caching and the Batch API at 50% lower cost | Prototyping multi-step prompts and building apps on Gemini, image, video and speech models |
Step 3: Rebuild a workflow as a skill in Gemini
The Gemini Apps Help article "Create & manage skills for Gemini Apps" lists several ways to create a skill. For an Opal migration, the manual route gives you the most control:
- Go to gemini.google.com, click Customize in the sidebar (under More if you don't see it), then Skills at the top.
- Click Create then Create manually.
- Enter a name, a description of what the skill does, and the instructions. This is where your copied Opal prompts go. Merge the steps into one ordered set of instructions ("First do X with the input, then use that result to do Y").
- Optionally click Add to attach reference files from your device, Google Drive, Google Photos or Notebooks, then click Create.
If you prefer working in files, you can write a SKILL.md yourself and use Create then Upload. You can select a single SKILL.md, or a folder or .zip with SKILL.md in its main folder. The skill name inside SKILL.md must be lowercase with hyphens, such as lecture-quiz-maker, and all uploaded files together must stay under 100 MB. Help also notes that you can import skills made on other platforms by uploading their SKILL.md files, which makes a SKILL.md a handy portable backup of your Opal logic.
Once it exists, type / (or @, if you have the updated shortcut) in any chat and pick the skill, or let Gemini apply it automatically when it judges the skill relevant. You can also reference one skill from another to build longer chains, which is the nearest thing to Opal's multi-step graph inside a chat.
Step 4: Rebuild it in Google AI Studio instead
For mini-apps that relied on media generation or several model calls, AI Studio is the better landing spot. Its welcome page offers Gemini, Nano Banana for images, Veo for video, Gemini TTS and Lyria for music, plus an app gallery with projects you can remix. Paste your copied prompts into a new prompt, test each former Opal step one at a time, and keep the sample output from your backup to compare against. When the chain works, get an API key in AI Studio and move it into code with the official SDKs.
Two practical points from the pricing and rate-limit docs: on the free tier, your content is used to improve Google's products, and rate limits apply per project rather than per API key, with daily request quotas resetting at midnight Pacific time. Linking a billing account moves a project to Tier 1, which also brings a spend-based limit of $10 per rolling 10 minutes.
Editor's note
Who this is for: anyone with mini-apps in My Drive > Opal or under "My Gems from Labs", and anyone who shared an Opal with a team or class. Who can skip it: people who only used classic Gems; those convert to skills automatically, though you should still download any knowledge files that won't carry over.
Gotchas and fixes:
- "My Opal disappeared from Drive": it shouldn't. Google says it won't delete or touch the files. Check My Drive > Opal while signed in to the same personal account you used for Opal.
- Skill upload fails: look for hidden binary files like .DS_Store or .pyc in the folder, make sure SKILL.md sits in the root folder, and check the name is lowercase-with-hyphens. Legacy .doc/.xls/.ppt files, audio, video and archives are not supported.
- Skill can't fetch a web page: skill scripts can't perform requests to external websites. Move that step to AI Studio or the API.
- Image or video step has nowhere to go: Create video and Create music don't work with skills yet, so rebuild those steps in AI Studio.
- Exact cutoff time: Google gives a date, not a time zone. Finish your backup by November 16 in your own time zone to be safe.
- 429 RESOURCE_EXHAUSTED in AI Studio: you hit a rate or spend limit. Wait and retry, shorten prompts or outputs, or request a higher limit.
FAQ
Will Google delete my Opal files?
No. According to the Opal FAQ, workflow files stay in My Drive > Opal and Google won't delete or touch them when the service turns off. They just stop running as apps after November 17, 2026.
Will my Opal mini-apps turn into skills automatically, like Gems?
No. Classic Gems are transitioned to skills automatically, but the Opal FAQ says existing Opal workflows will not migrate on their own. You need to recreate them as skills or prompts yourself.
Do I need a paid Google AI plan to use skills?
No. Gemini Apps Help says skills are available without a Google AI subscription and can be used in your chats. You do need to be 18 or over and signed in.
Related reading on this blog: NotebookLM Playbook: PDFs to Briefs and Audio Overviews if your Opal apps turned documents into summaries or audio, n8n Playbook: Draft Inbox Replies With an AI Agent for workflows that need real automation outside a chat, and Antigravity CLI Setup: Move From Gemini CLI Step by Step for another Google tool migration.
Copy your prompts this week while the editor still opens; rebuilding is easy, but rediscovering lost prompt logic is not.
See the official screenshots at the end of this post. Image credit: my own screenshots of the public opal.google page, the Opal FAQ on developers.google.com and Gemini Apps Help (support.google.com).
Last verified: 2026-11-11
Sources: Opal (opal.google), Opal FAQ, About the transition from Gems to skills, Create & manage skills for Gemini Apps, Gems from Google Labs help, Google Drive: Download a file, Google AI Studio, Gemini API pricing, Gemini API rate limits.
댓글
댓글 쓰기