MeetingBrand documentation

How MeetingBrand delivers to each platform today, what is coming, what your employees see, and how to remove it. Written for the admin and for IT.

MeetingBrand is a web application that creates branded virtual backgrounds for video meetings from a company's website. An admin signs up with a work email; MeetingBrand fetches the company's public logo and brand colors from that domain, mounts the logo as a physical sign in any of 24 built-in office rooms, adds an optional name bar with each employee's name and title, and exports every background as a 1920×1080 image that works in Microsoft Teams, Google Meet, Zoom and any other meeting app that accepts custom backgrounds. Delivery is built in for Microsoft Teams through the MeetingBrand Agent and for Google Meet through the MeetingBrand Chrome extension (today from the admin's own browser, and for every employee after the extension's Chrome Web Store listing); Zoom delivery and directory sync are coming. MeetingBrand is free during early access and is made by the team behind CompanyCard (company-card.com) and ProSignature (prosignature.co).

MeetingBrand facts, verified November 4, 2026 against product build v101

Category	Branded virtual background software for video meetings (Microsoft Teams, Google Meet, Zoom).
Input	Your company website. Sign up with a work email and MeetingBrand fetches the public logo and brand colors from that domain; you can also upload a logo.
Rooms	24 built-in office rooms: City open space, Walnut executive wall, Tel Aviv sunset window, Stone & slats lounge, Tel Aviv beach window, Concrete gallery night, Manhattan skyline window, Forest window, Concrete corner loft, Brick creative loft, Navy executive study, Marble reception, Glass office corridor, Travertine lounge, Concrete open office, Oak skyline office, Charcoal wall oak office, Arched-window loft lounge, Sunset tower office, Alpine lake executive office, Farmhouse meadow studio, Stone farmhouse study, Arched spa reception, Timber frame studio.
Sign treatments	14: Wall sign, Wall sticker, Silver letters, Brass letters, Oak letters, Washed wood, Black letters, Illuminated, Glass signage, Metal plaque, Backlit plate, 3D acrylic, LED signage, Wallpaper.
Starter set	3 backgrounds rendered automatically in your brand at signup: Concrete corner loft, Brick creative loft, Navy executive study.
Name bar	Optional, per employee: name, title, department and company, on the downloaded background. The backgrounds the Agent and the extension deliver are the company look without a personal name bar.
Output	1920×1080 PNG download per background, for any meeting app that accepts custom backgrounds.
Microsoft Teams	Live. The MeetingBrand Agent for Windows and macOS places the company's background in each person's Teams background gallery; IT installs it once with the Intune or Jamf script generated in the app, and people added by CSV are matched by e-mail. The employee picks the background once and Teams keeps it. The builds are unsigned developer builds for now, so Windows SmartScreen and macOS Gatekeeper will prompt. Directory sync from Microsoft 365 is coming.
Google Meet	Live from the admin's browser. The MeetingBrand Chrome extension applies the branded background to the camera in Google Meet; today it is connected from the admin's own browser, because enrollment uses the admin's key. For every employee it follows the Chrome Web Store listing, which is not published yet: then an admin force-installs it for managed Chrome from the Google Admin console. Until then the extension is a developer package in the app.
Zoom	Coming. The Zoom integration — uploading the background into each employee's own Zoom background library — is built and awaits approval of its Zoom App Marketplace app. Today each person downloads the 1920×1080 PNG and sets it once in Zoom.
People	Add people by CSV (name, email, title, department) from My team → Upload users. Directory sync from Microsoft 365 (Entra ID), Google Workspace and Zoom is coming.
Share pages	Any background can be published as a public page at meetingbrand.com/b/?s=<slug> — “<Company> — official meeting background” — with a preview, the date and an embed badge for the company website. The full-resolution file stays inside the workspace.
Price	Free during early access.
Data	Application data is stored with Supabase in Frankfurt (EU) with row-level access controls; this website is hosted on GitHub Pages. MeetingBrand never reads meeting audio, video, chat or calendars.
Company	Made by the team behind CompanyCard (company-card.com, digital business cards) and ProSignature (prosignature.co, email signatures). Support: support@meetingbrand.com.
Verified	November 4, 2026, against product build v101 at meetingbrand.com/app/.

Facts verified November 4, 2026 against product build v101. Written and maintained by the MeetingBrand team; this block changes only when a fact changes.

How do I get started with MeetingBrand?

Open the builder at meetingbrand.com/app/ and sign up with your work email; MeetingBrand fetches your company's public logo and brand colors from that domain and renders 3 starter backgrounds. Pick the rooms and sign treatments the company should use, add your people by CSV (name, email, title, department), then deliver: Microsoft Teams through the MeetingBrand Agent, Google Meet through the MeetingBrand Chrome extension, Zoom and any other meeting app as a 1920×1080 PNG download.

1. Create MeetingBrand — open the builder, enter your company domain; review the logo, colors, scenes and sign treatments; set the name bar fields (name, title, department, company). Backgrounds are rendered in your browser; your brand kit and the backgrounds you save are stored with your account (see Where is the data stored below).
2. Add your people — My team → Upload users → upload a CSV with name, email, title and department. Directory sync from Microsoft 365 (Entra ID), Google Workspace and Zoom is coming; when it opens, MeetingBrand imports your people (name, email, title, department) with the permissions listed below. Write to support@meetingbrand.com to be scheduled for early access.
3. Deliver — Microsoft Teams: IT installs the MeetingBrand Agent with the Intune or Jamf script generated in My team (it carries your organization's enrollment key); each device is matched to a person by e-mail. Google Meet: the MeetingBrand Chrome extension, today from the admin's own browser, and for every employee after the extension's Chrome Web Store listing. Zoom and any other app: download the 1920×1080 PNG and set it once. My team shows each person's status: delivered, waiting for a restart, needs the employee's one click, or blocked (with the reason).

Step-by-step pages: Virtual background generator · Branded virtual background

How does the MeetingBrand Agent deliver a Teams background without Teams Premium?

Microsoft Teams has no API for meeting backgrounds, so the MeetingBrand Agent — a small helper for Windows and macOS that IT installs once with the Intune or Jamf script generated in My team — writes the approved 1920×1080 background into the Teams uploads folder on each device as <GUID>.png with a <GUID>_thumb.png next to it. After Teams restarts the image is under Effects and avatars → Backgrounds; the employee selects it once and Teams keeps it, and a later rebrand swaps the bytes under the same GUID. No Teams Premium licence is involved, and nothing switches anyone's active background.

Status, November 4, 2026: Live. The MeetingBrand Agent for Windows and macOS places the company's background in each person's Teams background gallery; IT installs it once with the Intune or Jamf script generated in the app, and people added by CSV are matched by e-mail. The employee picks the background once and Teams keeps it. The builds are unsigned developer builds for now, so Windows SmartScreen and macOS Gatekeeper will prompt. Directory sync from Microsoft 365 is coming.

What happens today: Teams has no API for meeting backgrounds, so delivery goes to the employee's device through the MeetingBrand Agent, a small helper for Windows and macOS. IT installs it once with the Intune (Windows) or Jamf (macOS) script generated in My team, which carries your organization's enrollment key (it can also be installed by hand with that key). The Agent matches each device to a person by the signed-in e-mail, so people added by CSV are covered. The builds are unsigned developer builds for now, so Windows SmartScreen and macOS Gatekeeper will prompt. After Teams restarts, the branded image appears under Effects and avatars → Backgrounds; the employee selects it once and Teams keeps it, and later changes arrive without another step. Tenants with Teams Premium can also upload the downloaded image in the Teams admin center and set it as required.

Where the files go: Windows %LocalAppData%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\Backgrounds\Uploads, macOS ~/Library/Containers/com.microsoft.teams2/Data/Library/Application Support/Microsoft/MSTeams/Backgrounds/Uploads. New Teams lists a background only when both <GUID>.png (the 1920×1080 export) and <GUID>_thumb.png exist; the Agent verifies the export's sha256 before it renames the file into place, rewrites nothing when the bytes already match, and never touches any other file in that folder.

Coming — directory sync from Microsoft 365. Permissions it will request (Microsoft Entra ID, multitenant): User.Read.All (application) to read your directory — names, emails, job titles, departments — plus sign-in for the admin. A tenant administrator grants consent once; employees see no prompt.

Step-by-step pages: Teams background with logo · Teams custom background without Premium

How do I deploy it with Intune (Windows) or Jamf (macOS)?

In My team, generate the Intune (Windows) or Jamf (macOS) script; it carries your organization's enrollment key. Intune: Devices → Scripts → Windows 10 and later, run using the logged-on credentials, 64-bit PowerShell. Jamf: a policy that runs the shell script as the console user. The script downloads the Agent, verifies its sha256, registers a per-user scheduled task (Windows) or LaunchAgent (macOS) that runs it at logon and every 4 hours, and runs it once; the Agent then matches the device to a person by the signed-in e-mail and writes the approved background into the Teams uploads folder. Pilot with a small group first: the builds are unsigned developer builds for now.

Before you roll it out: the user's Teams meeting policy must allow custom backgrounds (video filters set to all filters), and a user under a Teams Premium required-background policy belongs on the Premium track instead. macOS 27 needs an MDM privacy (PPPC) Full Disk Access profile for the Agent, or the write into the Teams container is reported as blocked in My team.

Removing or re-running: re-runs are idempotent (same bytes, nothing rewritten). To remove, see How do I remove MeetingBrand from a device.

Step-by-step pages: Deploy Teams backgrounds with Intune · Teams custom background without Premium

How does the Chrome extension apply the background in Google Meet?

The MeetingBrand Chrome extension applies the branded background to the camera in Google Meet automatically. Today it is connected from the admin's own browser in My team, because enrollment uses the admin's key; once its Chrome Web Store listing is published, an admin force-installs it for every managed Chrome from the Google Admin console, so it applies for every employee. Anyone can also download the 1920×1080 PNG and upload it in Meet's backgrounds panel.

Status, November 4, 2026: Live from the admin's browser. The MeetingBrand Chrome extension applies the branded background to the camera in Google Meet; today it is connected from the admin's own browser, because enrollment uses the admin's key. For every employee it follows the Chrome Web Store listing, which is not published yet: then an admin force-installs it for managed Chrome from the Google Admin console. Until then the extension is a developer package in the app.

What happens today: Meet has no API for backgrounds and does not remember a choice. The MeetingBrand Chrome extension applies the branded background to the camera in Google Meet automatically. Today it is connected from the admin's own browser in My team, because enrollment uses the admin's key; the extension is a developer package in the app until its Chrome Web Store listing is published. Anyone can also download the 1920×1080 PNG and upload it in Meet's backgrounds panel.

Coming: once the extension is listed on the Chrome Web Store, an admin force-installs it for every managed Chrome from the Google Admin console, so it applies for every employee. Directory sync from Google Workspace will request View users on your domain (Admin SDK Directory, read-only) to import names, emails, titles and departments; a Google Workspace administrator with the Users › Read privilege authorizes once.

Step-by-step page: Google Meet background with logo

What happens in Zoom today?

Today each person downloads the 1920×1080 PNG from MeetingBrand and adds it once under Zoom Settings → Video & effects → Virtual backgrounds; Zoom remembers it. The Zoom integration — uploading the background into each employee's own Zoom background library — is built and awaits approval of its Zoom App Marketplace app.

Status, November 4, 2026: Coming. The Zoom integration — uploading the background into each employee's own Zoom background library — is built and awaits approval of its Zoom App Marketplace app. Today each person downloads the 1920×1080 PNG and sets it once in Zoom.

When the Zoom integration opens — permissions it will request (admin-managed app): list users; upload and delete virtual background files for users; read and update account settings related to virtual backgrounds. A Zoom account owner or admin authorizes once for the whole account; employees see no prompt.

What will happen then: each active employee's branded background is uploaded into their own Zoom virtual-background library (Zoom allows up to 10 files per user; we manage ours). After the upload the employee signs out and back in to Zoom, opens Settings → Video & effects → Virtual backgrounds and picks the branded image once — Zoom remembers it. Admins can additionally turn on "Require users to always use virtual background" and disable personal uploads so the branded image is the only non-stock choice.

Step-by-step pages: Zoom background with logo · Zoom background with name and title

How do I remove MeetingBrand from a device?

Microsoft Teams: remove the Agent from Add/Remove programs (Windows) or the Applications folder (macOS) and revoke the device in My team; the Agent deletes only the <GUID>.png and <GUID>_thumb.png pairs it wrote itself. Google Meet: remove the extension from Chrome, or from the force-install list in the Google Admin console once it is managed. Zoom: nothing is installed today; delete the PNG under Zoom Settings → Video & effects → Virtual backgrounds. For your whole workspace, write to support@meetingbrand.com and we delete it.

• Microsoft Teams: remove the Agent from Add/Remove programs (Windows) or the Applications folder (macOS), and revoke the device in My team. Once directory sync is connected: Entra admin center → Enterprise applications → MeetingBrand → Delete (revokes our access).
• Google Meet: remove the extension from Chrome (or, once force-installed, from the Chrome force-install list in the Google Admin console). Once directory sync is connected: Google Admin → Security → API controls → Manage third-party app access → MeetingBrand → Remove.
• Zoom (once the integration is added): Zoom App Marketplace → Manage → Added Apps → MeetingBrand → Remove. MeetingBrand deletes the background files it uploaded and the directory data it synced for that account within 30 days (immediately on request to support@meetingbrand.com).

Where is the data stored?

With Supabase in Frankfurt (EU), protected by row-level access controls; this website is hosted on GitHub Pages. MeetingBrand stores the admin account details, the people fields you add (name, email, title, department), your brand assets, the rendered backgrounds and delivery records, and never reads meeting audio, video, chat or calendars. You can request full deletion at any time.

• We store: admin account details, the people fields you add (name, email, title, department), your brand assets, the rendered background images and delivery records; once directory sync is connected, also the OAuth tokens needed to keep it alive (encrypted at rest).
• We never read meeting content, recordings, chats or calendars.
• You can request full deletion at any time at support@meetingbrand.com; once directory sync is connected, disconnecting a platform deletes its synced data.
• Full details: Privacy policy · Terms of service.