Everything you need to get Sync View working with your browser and Discord.
Before you begin, make sure you have:
Sync View requires a small companion app (SyncView.exe) that runs on your computer. This app bridges your browser and Discord.
SyncView.exe — the setup wizard will guide you through registrationabout:addonssync-view.xpiInstalling unsigned .xpi files requires Firefox Developer Edition, Nightly, or ESR. In about:config, set xpinstall.signatures.required to false. Standard Firefox will block unsigned extensions.
about:debugging#/runtime/this-firefoxmanifest.json from the project rootFirefox setup is complete! No additional configuration needed — the native messaging host is registered automatically by the installer or setup wizard.
chrome://extensions/chrome/ folder from the project (or dist/extension-chrome/ after building)Chrome requires the extension ID to be explicitly allowed in the native messaging host manifest. This is an extra step compared to Firefox.
chrome://extensions/ page, find the Sync View extensionabcdefghijklmnopqrstuvwxyzabcdef)Chrome's native messaging security model requires each extension to be explicitly allowed by ID. Firefox uses extension names instead, so this step is automatic. The ID changes if you reload the extension from a different folder, so you may need to update it.
edge://extensions/edge/ folder from the project (or dist/extension-edge/ after building)Edge uses the same Chromium native messaging model as Chrome, so the same registration step applies.
edge://extensions/ page, copy the Sync View extension IDYou can enter multiple extension IDs separated by commas. Both browser extensions will work simultaneously.
Discord does not show your own Rich Presence status to you. You need a second account or a friend to verify it's working. The Sync View popup and SyncView.exe activity log are the best way to confirm locally.
Sync View has three components that work together:
A content script runs on supported streaming sites and extracts metadata — title, artist/channel, playback progress, thumbnails, and live status. It uses the Media Session API where available, with DOM selector fallbacks for reliability. The extension sends this data to the native messaging host.
A headless process that the browser launches automatically via the native messaging protocol. It receives media data from the extension via stdin/stdout and forwards it to Discord's local IPC named pipe. This is the bridge between your browser and Discord.
A desktop GUI app that handles first-time setup, registers the native messaging host in the Windows registry, and provides settings, an activity log, and connection monitoring. It also checks for updates.
All communication is 100% local. No data is sent to any server — your browser talks to a local process, which talks to Discord via a local pipe.
Open SyncView.exe and click the gear icon to access settings.
Automatically launch SyncView when you log in. Useful if you always want Rich Presence active.
When you close the window, SyncView minimizes to the system tray instead of exiting. It keeps running in the background.
Launch directly to the system tray without showing the window. Best used with "Start with Windows".
Enter your Chrome and/or Edge extension IDs here. This is required for Chromium-based browsers to communicate with the native messaging host. Separate multiple IDs with commas.
Re-creates the native messaging manifest files and updates the Windows registry entries for all browsers. Use this if you moved the install directory or if the native host connection is broken.
Configuration is stored at %APPDATA%\SyncView\config.json.
syncviewhost.exe exists in the same directory as SyncView.exechrome://extensions/ or edge://extensions/1482383187882545233HKCU\Software\Mozilla\NativeMessagingHosts\youtube_discord_rpcpath field must point to the actual location of syncviewhost.exedocument_idlesyncviewhost.exe via a shared fileNo. Sync View is 100% local. Your browser extension talks to a local process via native messaging (stdin/stdout), which then talks to Discord via a local named pipe. No data ever leaves your machine.
No. SyncView.exe is only needed for first-time setup and configuration. The browser extension communicates directly with syncviewhost.exe, which the browser launches automatically when needed.
Yes! Each browser launches its own instance of the native messaging host. However, Discord only shows one Rich Presence status at a time — the last browser to send an update wins.
No. Discord Rich Presence only works with the Discord desktop app. The web version does not support local IPC connections.
Yes, that's the point! Your Discord Rich Presence is visible to friends and anyone who can see your profile. If you want to stop sharing, simply pause the media or disable the extension. You can also disable Rich Presence in Discord Settings → Activity Privacy.
Chrome and Edge use a stricter security model for native messaging. Each extension must be explicitly allowed by its unique ID. Firefox uses a different mechanism (extension names) that doesn't require this step.
Yes! Sync View is MIT licensed and fully open source. View the code, report issues, or contribute on GitHub.