LiveLoop Databus LiveLoop
Databus
LiveLoop
Features Solutions Tools Compare Guides Pricing
All products
Education
Finance & Operations
FinDeckAccounting & analytics Soon StockWiseInventory & stores Soon TaskDeckTasks & workflows Soon PeopleDeckHRMS & payroll
Sales & Support
LeadDeckSales & admissions CRM Soon TicketDeckSupport service desk Soon ConnectlyCommunity & messaging LiveLoopVideo meetings
Property & Mobility
AI
AskWiseAI assistant Soon
Blog

Share the screen, not the chaos

Screen sharing is the moment an online class goes quiet — the pause, the wrong window, the audio nobody hears. It is also entirely learnable. This guide covers the three sharing modes and when each is right, the audio checkbox everyone misses, phone realities, and the permission traps that block sharing at the worst moment.

Practical guide, written August 2026. Data and quality figures are planning estimates that vary with platform, settings and network conditions; measure your own sessions where precision matters.

Full screen, window, or tab — the decision that matters

Every platform offers the same three choices, and picking deliberately prevents most sharing accidents. Full screen shows everything you see — powerful for demonstrations that hop between apps, and dangerous for notifications, personal tabs and the email preview that pops up mid-class. Window shares one application only: the safest default for teaching from a deck or a PDF, because nothing outside that window can appear. Tab sharing, in browsers that offer it, shares a single browser tab and is the only mode on most platforms that carries the tab's audio smoothly — which makes it the right answer for playing a video. The teacher's rule of thumb: window for documents, tab for videos, full screen only when you genuinely need to switch between applications, with notifications silenced first.

The audio problem, solved once

'Can you hear the video?' has one cause: screen video and screen audio travel separately, and sharing audio is an explicit checkbox — 'share tab audio' or 'share system audio' — offered at the moment you pick what to share. Tick it when your content has sound; leave it off otherwise so the class does not hear your notification pings. Two related habits: play the video from a tab rather than a desktop player when you want its sound, since tab audio is the most reliably supported path; and remember your microphone stays live while sharing, so the class hears both you and the content — mute yourself if the content should stand alone.

Step by step

  1. 1

    Silence the machine

    Notifications off, personal tabs closed or parked in another window, desktop presentable if full-screen is possible.

  2. 2

    Pick the narrowest mode that works

    Window for documents, tab for videos with sound, full screen only for multi-app demonstrations.

  3. 3

    Tick audio only when content has sound

    The share-audio checkbox at selection time — on for videos, off for everything else.

  4. 4

    Keep students visible

    Second screen or device for the grid, or a window share that leaves the panel in view.

  5. 5

    Rehearse the handoff once

    If students will present, one 30-second practice share at the start of term saves ten mid-class rescues.

When students present: running the handoff

Student presentations are where sharing chaos concentrates, and the fix is a written micro-protocol the whole class knows. The host enables participant sharing for the slot, not the term. Presenters queue in the agreed order with files open before their turn — the ninety seconds of 'wait, it is downloading' is the single biggest time sink in student presentation days. Each presenter shares a window, not a full screen, sparing the class their notifications and wallpaper. The previous presenter stops sharing before the next begins, because two competing shares confuse every platform's focus. And the teacher keeps a copy of every deck as fallback: when a student's connection dies mid-presentation, the teacher shares the same file and the student continues by voice — the show goes on, and the student learns that presenting online is survivable. One rehearsal run in week one buys a term of smooth Fridays.

Teaching habits that make sharing invisible

The best-run online classes make sharing boring. Content queued before the session — the deck open, the video tab loaded and paused, the PDF at the right page — so switching takes seconds, not searching. A visual rhythm: never more than a few minutes on a static screen without something changing, a highlight, an annotation, a question, because a frozen slide reads as a frozen class on a phone. Narration that names what is on screen — students on small screens or weak connections follow the voice when the pixels lag. And the recording habit: sharing-heavy classes are precisely the ones worth recording, since the shared material replays perfectly for revision in a way a camera-on-whiteboard never does.

How LiveLoop applies this

LiveLoop shares full screen, window or tab from the browser with audio where you tick it, keeps the class visible alongside, and records the shared content cleanly for revision.

Go deeper: Screen sharing · Recording

Written by Databus Technology Solutions, the makers of LiveLoop. These guides describe how online classes behave in practice. Data figures are planning estimates that vary with platform, quality settings and network conditions; measure your own sessions where precision matters.

Frequently asked questions

Why is my share button greyed out or blocked?

On desktops, it is almost always an operating-system permission: the browser needs screen-recording permission granted in system settings (macOS is the classic case), after which a browser restart fixes it. In classes, hosts can also restrict sharing to themselves — if students should present, the host enables participant sharing. Sixty seconds of checking beats improvising a phone-camera-at-the-monitor workaround.

Can students share from a phone?

On browser-based platforms, phone screen sharing is limited by the mobile OS — where it works it shares the whole screen, notifications included. The practical classroom pattern: students share work by uploading or by camera, and reserve screen sharing for desktops; teachers who need phone-side presentation test it before the class that depends on it.

How do I share and still see my students?

Use two surfaces if you can — share from one screen or window while keeping the participant grid on another (a second monitor, or the phone joined as a second device on mute). Single-screen teachers should share a window rather than full screen, leaving a slice of the participant panel visible alongside.

Whiteboard or shared document instead of a slide deck?

For working problems live — maths, code, diagrams — a shared whiteboard or a document the class watches you type beats static slides, and it usually costs less data than camera-on-paper. Keep the deck for structure and the board for thinking; the mode switch itself re-captures attention.

Does screen sharing eat more data than video?

Depends entirely on motion. A still slide costs almost nothing after the first moment; a shared video clip or animated content behaves like streaming video for every attendee. If data-poor students matter, prefer slides-plus-voice for the heavy hour and keep video clips short — or point them at the recording for Wi-Fi-time rewatching.

What should I check before a class that depends on sharing?

Three things, two minutes: the OS permission (share something in a test call), the audio checkbox path for your content, and notifications silenced. Teachers who run this tiny preflight simply do not have sharing incidents; the incidents all live in the unprepared first attempt.

Two minutes of preflight; zero incidents.

Applied on every payslip, files generated for upload — per employee, per month.

Start free