productivity

Presentation Remote

Open a local PPTX or PDF on your computer and control it from a QR-paired phone, with current/next slide previews and speaker notes.

Local processing
About your filesFiles and content selected in this tool are processed in your browser and are not uploaded to a Browser Kitty backend.
Operation demo See the basic workflow in a short video.

About this tool

Presentation Remote is a browser presentation tool that opens a PPTX or PDF on the presenting computer and turns a phone into a remote control. The source document is parsed and displayed in the computer browser rather than uploaded to an application server. You can also present from the computer alone and pair a phone only when remote control is useful.

Phone pairing uses a two-way QR exchange to establish direct WebRTC. With Presenter View enabled, the phone can show low-resolution current/next slide previews and PowerPoint speaker notes. Those presentation-view data and control messages travel directly between the two browsers without a signaling server, STUN, or TURN.

Good for

  • Control a PPTX or PDF from a phone in a meeting room or classroom without installing a dedicated remote app or carrying a Bluetooth clicker
  • Keep the computer on the audience view while checking the current/next slides and speaker notes on the phone
  • Present a document in the browser without sending the source deck to an external conversion service
  • Use black screen, direct slide jumps, and touch or motion pointer controls from the same phone as page navigation

What it can do

Key capabilities available in this tool.

How to use

  1. Open Presentation Remote on the presenting computer and choose a PPTX or PDF file.
  2. Review the slide list and start full-screen presentation mode when needed.
  3. To use a phone, choose the phone-connect action on the computer and display the pairing QR code.
  4. Open Presentation Remote on the phone, choose phone control, and scan the QR code shown on the computer.
  5. Scan the response QR shown on the phone back on the computer to complete the direct WebRTC pairing on the reachable LAN.
  6. Use next/previous, swipe navigation, black screen, pointer, and slide-number controls from the phone.
  7. Use Presenter View for current/next previews and speaker notes, or turn it off from More when a simpler remote is preferred.

Supported

  • Input: PPTX and PDF, with a current UI limit of 150 MB per file. Parsing and presentation rendering run in the presenting computer's browser.
  • Phone pairing: direct WebRTC through a QR exchange. With no signaling server, STUN, or TURN, the computer and phone generally need to be on the same mutually reachable Wi-Fi/LAN.
  • Remote controls: previous/next, swipe navigation, black screen, direct slide jump, timer, and touch pointer; motion pointer and Screen Wake Lock are available on supported devices.
  • Presenter View: low-resolution current/next slide previews plus PowerPoint speaker notes. PDF files do not contain PowerPoint speaker notes.
  • Browsers: Chrome and Edge are the primary tested targets. Safari supports basic remote behavior where the required WebRTC APIs are available; Firefox is not a primary release-validation target.
  • Distribution: the root presentation-remote.html bundles the required runtime and does not use a runtime CDN, analytics tags, or telemetry.

Limitations and notes

  • This is not PowerPoint itself, so complex effects can render differently. Animations and transitions are shown as static content; export to PDF first when exact visual fidelity is more important.
  • Because there is no signaling server or STUN/TURN relay, phone pairing can fail on guest Wi-Fi, client-isolated networks, VPNs, or restrictive firewalls.
  • PDF files do not contain PowerPoint speaker notes, so Presenter View cannot show those notes for PDFs.
  • Starting full-screen presentation mode requires a user action on the presenting computer because of browser restrictions.
  • Screen Wake Lock, vibration, Device Orientation, and camera permissions depend on browser/OS support and permission settings.
  • Large or complex decks can use substantial device memory. When Presenter View is enabled, low-resolution previews and speaker notes are sent directly from the computer to the paired phone.

Frequently asked questions

Are PPTX or PDF files uploaded to a server?

No. The source document is parsed and rendered in the presenting computer's browser. When a phone is paired, only control/state data and, for Presenter View, low-resolution previews and speaker notes are sent directly between the two browsers over WebRTC.

Do the computer and phone need to be on the same Wi-Fi?

Generally yes. Pairing is direct and uses no signaling server, STUN, or TURN, so the two devices need to be mutually reachable on the same Wi-Fi/LAN. Guest networks, client isolation, or VPNs can prevent connection.

Does Presenter View work with PDF files?

Current and next slide previews are available, but PDF files do not contain PowerPoint speaker notes, so speaker notes are not shown.

Can I present without pairing a phone?

Yes. You can open the deck and present from the computer with keyboard or on-screen controls, then pair a phone only when remote control is useful.

What is sent to the phone when Presenter View is enabled?

Along with slide/state, remote, and pointer data, the computer sends low-resolution current/next previews and the current PowerPoint speaker notes directly over WebRTC. The source presentation file itself is not sent.

Offline version and source code

The root presentation-remote.html bundles the required runtime in one HTML file, so local PPTX/PDF parsing and presentation rendering can run without a runtime CDN. Phone remote traffic uses direct WebRTC DataChannel communication; pairing still requires a mutually reachable LAN and browser support/permissions for features such as QR camera access or motion sensors.

View source on GitHub