Sharing multiple screens and having participants choose which to view | Community
Skip to main content
New Member
August 18, 2026
Solved

Sharing multiple screens and having participants choose which to view

  • August 18, 2026
  • 3 replies
  • 34 views

I am preparing to host a bilingual meeting, where I will need to share multiple slide decks simultaneously, one in each language. Not all participants are comfortable in both languages, so I would like them to be able to choose if they want to view the deck in language A or language B. I do not want both decks in the same view. Ideally, I would have each deck appear as a different view option, similar to when multiple participants are sharing screens and attendees can choose which one to look at, but I’d like to do it from the same computer rather than needing to set up multiple computers as “participants.” As the host, I have copies of the decks in both languages and will be advancing the slides for both decks. Is this possible? 

 

Best answer by Don.z

Welcome to the Zoom community, ​@HMQ!

Thanks for explaining the use case. I can definitely see why you’d want to keep everything on one computer, especially when you’re managing and advancing both decks yourself.

The challenge is having those two independent shares come from the same host computer. Zoom doesn’t currently provide a reliable way for one host to publish two separate decks as two selectable share views from a single computer.

The dependable setup would be to have a second sharing source, for example:

  1. You share the Language A deck from your computer.
  2. A second participant or device (joined as co-host) shares the Language B deck.

Participants can then use View Options to switch between the two languages without having both decks in the same view.

I know that’s not quite the one-computer setup you were hoping for. Your idea makes a lot of sense from the attendee’s perspective, and the simultaneous sharing feature gets very close. The limitation is specifically on creating those two independent share sources from the same computer.

If keeping everything on one computer is important for your workflow, I’d also encourage you to submit this as a feature request through Zoom Feedback. That gives the product team a chance to see the use case and the value of being able to offer multiple selectable share views from a single host.

3 replies

Don.zAnswer
Community Manager
August 20, 2026

Welcome to the Zoom community, ​@HMQ!

Thanks for explaining the use case. I can definitely see why you’d want to keep everything on one computer, especially when you’re managing and advancing both decks yourself.

The challenge is having those two independent shares come from the same host computer. Zoom doesn’t currently provide a reliable way for one host to publish two separate decks as two selectable share views from a single computer.

The dependable setup would be to have a second sharing source, for example:

  1. You share the Language A deck from your computer.
  2. A second participant or device (joined as co-host) shares the Language B deck.

Participants can then use View Options to switch between the two languages without having both decks in the same view.

I know that’s not quite the one-computer setup you were hoping for. Your idea makes a lot of sense from the attendee’s perspective, and the simultaneous sharing feature gets very close. The limitation is specifically on creating those two independent share sources from the same computer.

If keeping everything on one computer is important for your workflow, I’d also encourage you to submit this as a feature request through Zoom Feedback. That gives the product team a chance to see the use case and the value of being able to offer multiple selectable share views from a single host.

HMQAuthor
New Member
August 20, 2026

Thank you! I appreciate your clear explanation of the options. It looks like borrowing a second device is the way to go for now, and I’ll submit a feature request as suggested.

Community Manager
August 20, 2026

Glad we could help clarify the options. I’ll mark this as the best answer so others in the community with a similar setup can quickly find the solution and understand the current limitation.


Thanks again for sharing such a thoughtful use case with the community!