Will Your Live Wallpaper Show Up on a Zoom or Teams Screen Share?
You've got a live wallpaper drifting behind your icons, you're about to hit "Share Screen" on a call, and a small, entirely reasonable worry shows up right before you click: is that thing going to be visible to everyone on the other end? Is it going to look unprofessional, eat bandwidth, or do something weird nobody expects? It's a question that never comes up with a static wallpaper, because a static image just sits there, but a live wallpaper is, by design, always doing something, and "always doing something" is exactly the kind of detail that gets noticed the moment it's broadcast to a room full of coworkers.
The short version is that it depends entirely on how you share your screen, not on whether you're running a live wallpaper at all. This post walks through exactly what determines visibility, what Gloomia does and doesn't pause for during a call, what it actually costs in bandwidth and CPU, a genuinely surprising interaction with audio-reactive wallpapers, and which wallpapers are worth switching to before a screen share that actually matters.
The one setting that decides everything: what you're actually sharing
Every major video call app, Zoom, Microsoft Teams, Google Meet, gives you a choice when you hit "Share Screen," and that choice is the entire answer to whether your wallpaper appears. Share your entire screen or desktop, and the call sends out a live feed of everything visible on that display, your open windows, your taskbar, and any part of the desktop that isn't covered by a window, including a live wallpaper animating away in that visible space. Share a specific window or application instead, a spreadsheet, a browser tab, a slide deck, and the call only captures the pixels inside that window's boundaries. The wallpaper sitting behind it, no matter how busy or calm, is never part of that feed, because it was never inside the region being captured in the first place.
This is exactly the same distinction that governs whether a wallpaper shows up when streaming to Twitch or YouTube through a capture tool: a full-desktop capture picks up whatever's genuinely visible, and a window-scoped capture doesn't. If you only ever share a single app window on calls, you can stop reading here. Your wallpaper was never at risk. The rest of this matters if you ever share your whole screen, which most people do at least occasionally, for a quick "let me just show you my desktop" moment or because switching between several apps mid-call is easier without re-picking a share target each time.
Does Gloomia pause the wallpaper for a call the way it does for games?
This is the part that surprises people, because it doesn't work the way you might expect from how Gloomia behaves during gaming. Rendering pauses automatically on a display once something fully covers it, whether that's a fullscreen game, a maximized browser, or a maximized call window, a rule covered in more depth in the gaming desktop wallpaper guide and the battery and GPU impact breakdown. The catch is that video call apps rarely run in that fully covering state on the display you're actually sharing. Most people keep the call window small, on a second monitor, or floating in a corner precisely so they can see their own shared content and the other participants at the same time. That means the display being captured usually isn't covered by anything, and the wallpaper keeps animating exactly as it would on any ordinary day, fully visible in the shared feed.
Compare that to a fullscreen game, which reliably claims the entire display the moment it launches, triggering the pause every time without you having to think about it. A video call almost never does that to the screen you're sharing, which is the core reason this behaves differently from the gaming case even though the underlying pausing rule is identical.
What it actually costs: a small, real bandwidth and CPU bump
Screen-sharing software doesn't send a fixed amount of data regardless of what's on screen. It encodes video, and like any video encoder, it spends more work and more bandwidth on frames that are changing than on frames that are static. A shared screen showing a still spreadsheet compresses down to almost nothing between updates. The same screen with a live wallpaper animating in the visible margins gives the encoder continuous motion to deal with, even if everything else on screen is perfectly still, which means a real, if usually modest, increase in the data being sent and the CPU spent encoding it.
How much this actually matters comes down to the same factor that determines GPU cost in general use: how visually dense the wallpaper is. A calm wallpaper like Starfield, Planet System, or Hue Drift moves slowly enough that the difference is close to unnoticeable. Something like Wormhole or Binary Black Holes, both built around constant, high-contrast motion filling most of the frame, gives the encoder meaningfully more to chew on if it's sitting in the visible part of an entire-screen share for the length of a long call. None of this competes with the call itself in any serious way on modern hardware, but if you're already on a weak connection or an older laptop juggling a call, a browser, and a handful of other apps, switching to a calmer wallpaper before an important screen share is a genuinely free way to shave a little load off the whole stack.
The distraction problem is bigger than the technical one
Bandwidth aside, the more common issue is simply that a moving background pulls attention away from whatever you're actually trying to present, a slide, a spreadsheet, a piece of code. That's true of any live wallpaper during a full-desktop share, but it's worth being specific about two wallpapers where the problem goes beyond distraction into outright confusion. Terminal fills the screen with a realistic, continuously typing console, complete with build logs, a git status, and a progress bar that never finishes, and Command Center runs a busy, cinematic ops-room dashboard with a world map and scrolling telemetry. Both are entirely simulated, no real commands are executing and no real data is being tracked, but glimpsed in the corner of a shared desktop during a work call, either one can genuinely read as something actually running on your machine, which is a strange thing to have to explain mid-meeting.
None of this is a knock on either wallpaper. They're genuinely well suited to a hacker or ops-room aesthetic when you're the only one looking at your desktop, or when you're the one presenting it on purpose. The point is narrower: if you're sharing your entire screen for a work call where the wallpaper isn't the point, a calm, quiet scene avoids both the distraction and the "wait, is that really running?" question entirely.
The audio-reactive surprise: it can react to the call itself
This is the detail most people don't see coming. Gloomia's four audio-reactive wallpapers, Aurora Flow, Spectrum Bars, Radial Pulse, and Waveform Ribbon, work by reading whatever audio your computer is currently outputting in real time, not your microphone. Normally that means they react to music or a game's sound effects and stay completely still while you're just talking into a mic, which is exactly the behavior covered in the audio-reactive wallpaper guide. A video call changes that equation, though, because the moment someone else on the call speaks, their voice comes out of your speakers as ordinary system audio, the same category of sound as music or a notification chime. If you're on speakers rather than headphones during a call, an audio-reactive wallpaper has no way to tell the difference between a colleague talking and a song playing, and it will pulse and shift right along with their voice.
That's not a bug or a privacy issue, nothing about the conversation is being recorded, analyzed, or sent anywhere, it's purely a live visual response to sound already leaving your speakers. But it does mean an audio-reactive wallpaper visible in a full-desktop share turns into a strange, twitchy backdrop that flares every time someone else speaks, which is worth knowing before it happens live rather than discovering it mid-call. Switching to headphones removes the effect entirely, since the call audio never reaches your speakers for the wallpaper to pick up, and choosing a non-audio-reactive wallpaper for calls sidesteps it just as easily.
What's actually private, and what isn't
It's worth separating the visual concern from an actual data concern, because they're different questions. Nothing about a video call, its audio, its participants, or its content is ever read, stored, or transmitted by Gloomia. The wallpaper reacting to speaker output, described above, is a purely local, real-time visual effect with nothing leaving your machine because of it. On the network side, the only wallpapers in the catalog that talk to the internet at all are Constellations, which draws the real night sky for your own coordinates, Orrery, which tracks real solar-system positions, and Asteroid Watch, which pulls a live NASA/JPL near-Earth-object feed, all covered in the real-data astronomy wallpapers guide. Every other wallpaper in the collection, including Terminal and Command Center despite how they look, runs entirely offline. None of the three real-data wallpapers reveal anything about a call either; the only thing worth considering with them is that Constellations is tied to your actual location, which is a reasonable thing to swap out for something else before sharing your screen with people you'd rather not hand your coordinates to at a glance.
A practical checklist before you hit share
Put together, the actual decision tree before an entire-screen share is short. If you only ever share a specific window or app, none of this applies, the wallpaper was never in frame. If you do share your whole desktop, switch to a calm wallpaper like Starfield, Planet System, or Hue Drift beforehand, since all three are free, quiet, and unlikely to distract or confuse anyone watching. Skip Terminal and Command Center for anything where the audience might mistake the simulation for something real. Put on headphones if you're running an audio-reactive wallpaper and don't want it visibly reacting to the other side of the conversation. And if bandwidth is genuinely tight, a calm wallpaper costs the encoder almost nothing extra, while a dense one like Wormhole adds a small but real amount of encoding work for the length of the share.
None of this requires paying for anything to test. Starfield, Planet System, and Hue Drift are free forever with no account needed, which makes them a reasonable default to leave running if you share your screen often and would rather not think about switching wallpapers before every call. If you're weighing whether the rest of the catalog is worth it beyond that, the free versus Pro breakdown lays out exactly what unlocking Gloomia Pro adds, separate from any of the screen-sharing behavior covered here.
The bigger point is that a live wallpaper isn't something you have to hide or apologize for on a work call. It's just another visible element on your desktop, subject to the exact same rules as an open browser tab or a messy taskbar: if you're sharing your whole screen, it's in the shot, and if you'd rather it weren't, either share a specific window or spend ten seconds picking something calmer first.
Frequently asked questions
Will my live wallpaper show up if I share my screen on Zoom, Teams, or Meet?
It depends on how you share. If you choose "entire screen" or "desktop," anything visible on that display, including your live wallpaper, goes out in the shared feed exactly as it looks to you, animation included. If you share a specific window or application instead, only that window's contents are sent, and the wallpaper behind it never appears.
Does Gloomia pause the wallpaper automatically during a video call?
Only under the same rule it always uses: rendering pauses on a display once something fully covers it, whether that's a game, a maximized browser, or a maximized call window. Most video calls don't run truly maximized on the display you're sharing, so the wallpaper usually keeps animating in the background, unlike a fullscreen game, which reliably triggers the pause.
Will a live wallpaper slow down my video call or use more bandwidth?
A little, and only while it's actually visible in an entire-screen share. Screen-sharing tools encode more data when more of the frame is changing, so a wallpaper with constant motion adds some encoding work next to a static desktop. For a calm wallpaper like Starfield or Hue Drift the difference is minor. For a visually dense one like Wormhole or Binary Black Holes filling the screen, it's more noticeable, though still small next to the cost of the video call itself.
Can audio-reactive wallpapers react to what's said on a call?
Yes, if you're on speakers rather than headphones. Aurora Flow, Spectrum Bars, Radial Pulse, and Waveform Ribbon read whatever audio your computer is currently outputting, not your microphone. On a call, other people's voices play through your speakers as system audio, so the wallpaper will pulse along with them the same way it would with music, since it can't tell the difference between a voice call and a song.
Is it a privacy risk to have a live wallpaper running during a work screen share?
No, in terms of data. Gloomia doesn't read anything about your call, your screen-sharing app, or your other windows, and most of the catalog needs no network access at all. Only three wallpapers, Constellations, Orrery, and Asteroid Watch, connect to the internet, and only to pull their own real astronomical and near-Earth-object data, nothing related to the call. The real risk during a screen share is visual, distraction or confusion, not data leaving your machine.
Which wallpapers are safest to leave running during a work call?
The calm, free ones: Starfield, Planet System, and Hue Drift all move slowly and read as background rather than content. Terminal and Command Center are worth avoiding for a serious screen share specifically because they look like real system activity at a glance, which can genuinely confuse someone glancing at your shared screen.