How to share your screen with Gemini Live

To share your phone screen with Gemini Live, open Live in the Gemini mobile app, choose Turn on screen sharing, and follow the device prompts. The full screen is shared, so prepare what you want to show before starting; Google documents the controls in its mobile Live guide↗ (opens in a new tab). Ask a focused question about the visible work, then stop sharing when you are done. fenbs can keep the checked result and next step so another session can continue without repeating the demonstration.

How do you start sharing your phone screen?

1. Prepare the material you want to discuss. Close or move away from unrelated information before sharing, because the full screen is the shared input.
2. Open the Gemini mobile app and choose Live, or swipe left to enter Live.
3. Choose Turn on screen sharing and follow the prompts on your device. Review the request before allowing capture.
4. Show the work you want to discuss and name the specific part you want help with.
5. Ask one question, check the answer against the visible material, and use Turn off screen sharing when you have finished showing it.

On Android, Google also documents a route from outside the app: invoke Gemini and choose Share screen with Live. Android requires Live notifications for screen sharing. Start with a harmless example you can recognize, such as a draft layout with no private information, before using the workflow for ongoing work.

What exactly can Gemini see?

For this mobile workflow, Google describes sharing the full screen. Do not treat it as permission to see just the one paragraph you are discussing. Prepare the phone so that material you do not intend to show is not on display. Avoid opening private conversations or unrelated account information while the screen is being shared.

A useful opening is: “I am showing a draft event page. Look only at the heading and registration instructions. Tell me what a first-time visitor might misunderstand.” That is an example request, not a technical restriction on capture. Your words narrow the question; they do not narrow the area being shared.

Showing a physical object is a different job. Use the separate Gemini Live camera guide when the useful information is in front of the phone rather than on its screen. Keeping the input choice clear also makes it easier to explain what evidence you used later.

Do Android, iPhone, and desktop use the same controls?

Google documents mobile Live for Android and in its iPhone and iPad help↗ (opens in a new tab). Use the Live screen-sharing controls and your device’s prompts. The iOS help currently contains some Android-style instructions, so do not assume an Android notification-card route or a particular operating-system dialog name applies to an iPhone.

The mobile requirements name signed-in personal or eligible work and school accounts. Google’s mobile availability page↗ (opens in a new tab) includes the US. Check eligibility for your account before troubleshooting a missing feature, especially if an organization manages access. The current Live help has inconsistent age wording, so use Google’s account guidance rather than treating a single quoted age as a universal rule.

Desktop Chrome is a separate experience. Google’s Chrome Live guide↗ (opens in a new tab) describes sharing selected browser tabs and page content, not general access to every desktop application. Those browser controls do not turn an ordinary Gemini web chat into the mobile screen-sharing workflow described here.

How do you stop sharing or recover after a pause?

Use Turn off screen sharing in the app to stop the shared input. Android also provides Stop sharing on the Screen Sharing notification card. Google says that putting Live on hold or locking the screen stops screen sharing, and you must start sharing again afterward. Muting is different: it does not, by itself, stop screen sharing.

Check that distinction before switching to something private. A quiet conversation is not evidence that capture has ended. Stop sharing deliberately when the visible part of the task is complete, then confirm the state before opening another piece of work. If you resume later, say what you are showing again instead of assuming the conversation has the current view.

When a session seems to lose the screen, first check whether you locked the phone or put Live on hold. Then restart sharing using the documented control. Keep the next question simple enough to tell whether the assistant is discussing the current content. Avoid changing unrelated permissions or inventing a menu path from a different device.

What questions work well with a shared screen?

Choose something you can verify on the display. You might ask for a plain-language explanation of visible instructions, a review of a draft layout, or questions to ask before approving a design. State the goal and the review criteria. “Help with this” leaves you with less to check than “Explain the two choices shown and tell me what information is missing.”

• For understanding: “Explain this visible instruction in simpler words, and tell me which part you are referring to.”
• For review: “Check the wording against these three requirements and keep your observations separate from suggestions.”
• For comparison: “Compare these two visible versions using readability and clarity. Do not assume either is approved.”
• For a handoff: “Summarize what we checked, what is still uncertain, and the next action I chose.”

Check the answer against the screen and the source material. A confident explanation does not settle whether a claim is true or a change is authorized. If you are choosing an assistant for a research task, see ChatGPT versus Gemini for research. For work on an editable draft, Claude versus Gemini Canvas covers a neighboring workflow.

What should you keep when the conversation ends?

Keep the result in words that make sense without the display: what you showed, what you checked, what you decided, and what happens next. Name the version or source when it matters. “Fix the issue we saw” gives a future reader little help; “Check the registration instructions against the approved event details” explains the work.

Saving text after a chat is a different job from providing a live screen as input. The separate guide to saving Gemini chats covers that need. If you are moving an older conversation from another assistant, see transferring a Claude chat to Gemini. For continuing the current work, a short, checked summary is a useful place to start.

How to keep screen-review findings with fenbs

1. Create a free account.
2. Write what you showed and the useful result you checked. Keep private details out and mark unanswered questions clearly.
3. Add a task for the next action, including the source or version someone needs to review.
4. Connect Gemini to fenbs. Use a personal account that meets the connection requirements.
5. Save where you stopped, then ask the next connected AI to read that record before continuing on any device.

Google’s custom-app guide↗ (opens in a new tab) explains that separate connection and its US personal-account requirements. Connecting it does not guarantee it can be used during Live. fenbs helps when a screen review creates work you need to resume. If you only need a quick explanation, keeping a separate record may add little. How fenbs works shows the shared work record; find other practical workflows in AI at work.