Bitfocus AS
logo
logo
Bitfocus AS
logo
logo
Sign upSign in

Loading...

Bitfocus

Subscribe to our newsletter

The latest news, articles, and resources, sent to your inbox.

FacebookInstagramGitHubYouTubeLinkedIn

Products

  • Buttons
  • Companion

Integrations

  • Supported Devices
  • Developer Community
  • Connection Development

Support

  • Support Overview
  • Documentation
  • Video Tutorials
  • Community Forum

Sales

  • Resellers & Integrators
  • Buttons Pricing

Updates

  • Case Studies
  • Events & Trade Shows
  • Press Releases
  • Product Updates
  • Webinars

Legal

  • Legal Overview
  • Privacy Policy
  • Buttons EULA
  • Terms & Cookie Policy

Company

  • About us
  • Press kit
  • Careers

© 2026 Bitfocus AS. All rights reserved.

Surface compatibility
Docs for
Overview
Getting started
What is Bitfocus Buttons?
Install Buttons and get started
Manage your Buttons license
Activate Buttons offline
Find your way around Buttons
Create your first backup
Add an ATEM connection
Choose a control method
Choose an installation path
Install Buttons on Debian or Ubuntu
Understand HA clustering
Kubernetes HA
Update or remove Buttons
Positions
Understand positions
Create a position
Add controls and sections to a position
Create your first button
Use a connection's presets
Build more capable button actions
Add more feedback to a button
Organize controls in a section
Shift Section
Organize controls with a Folder Section
Add a Popover Section
Build and reuse a Shared Section
Build a Router Section
Understand Custom Routers
Custom Router panel
Surfaces
Surface compatibility
Add and attach a surface
Device orientation
Connections
Update a connection's module safely
Monitor and troubleshoot a connection
Router integrations
VideoHub and AJA KUMO
Utah Scientific BPS
Generic SW-P-08
Nevion VideoIPath
Arkona BLADE//runner
Routing
Physical routing
Configure ports and labels
Take a physical route
Understand route status
Topology graph
Routing Presets
Get started with virtual routing
Configure Nested Shapes
Reverse routing
Tielines
Routing Projects
Routing settings
Troubleshoot a route
Tally
Understand the Tally system
Send ATEM tally and labels to a UMD
Interpret Active Tally state
TSL/UMD connections
Diagnose tally problems
NMOS
Understand NMOS in Buttons
Connect Buttons to an NMOS Registry
Built-in Registry Server
Configure NMOS connections
Discover and adopt
Browse the NMOS inventory
Manage NMOS multicast addresses
Diagnose NMOS problems
Understand Cuelists
Build a Cuelist
Read and advance a running Cuelist
Control a Cuelist from a Position
Workflows
Understand workflows
Build your first workflow
Reuse a group of workflow nodes safely
Troubleshoot a workflow
Recipes
Sequence a timed automation
Call an HTTP endpoint from a workflow
REST endpoint
Use variables
Understand variable scope
Understand nested variables
Update expressions for v1.8
Plan and use Tags
Access
Create and manage users
Create roles and assign permissions
Grant access to specific resources
Show different controls by role
Sessions
Set up PIN and NFC sign-in
SSO
Get started with SSO
Connect a generic OIDC provider
Connect LDAP or Active Directory
Map identity claims to roles
Secure a Buttons deployment
Integrations
External control
Connect to Bitfocus Listener
USB Relay
Install USB Relay on Windows
Install USB Relay on macOS
Install USB Relay on Linux
Install USB Relay on a Raspberry Pi
Get started with the Control API
Secure and monitor the Control API
Control API reference
API reference
Administration
Enable and manage installable features
Services and health
Configure and monitor scheduled backups
Restore a backup and verify it
Export or import Buttons configuration
Store and rotate connection secrets
Replace the HTTPS certificate
HA backup and recovery
Settings
Collect support information
Reference
Glossary
Button Inspector reference
Network ports reference
Expressions
Internal actions reference
Routing Presets panel reference
Startup configuration reference
Workflow nodes
Connection workflow nodes
Workflow workflow nodes
Internal workflow nodes
Position workflow nodes
API workflow nodes
Utility workflow nodes

Loading...

Previous
← Surfaces
Next
Add and attach a surface →
Contact support →
You are viewing documentation for Buttons 1.8.See the docs for Buttons 1.6
Buttons/Surfaces/Surface compatibility

Surface compatibility

Before you cable up a panel or hand one to an operator, Buttons can tell you immediately whether it's a model it knows how to drive, so you find out during discovery, not partway through building a Position around it. Buttons doesn't publish a separate compatibility list for this: the product itself is the up-to-date source, because the set of supported panels and integrations grows as Bitfocus adds drivers for new hardware.

Before you begin#

  • Enough access to Connect → Surface to view discovered devices (read access to Surfaces). Adopting a supported device or creating one manually needs create permission, see Add and attach a surface.
  • Checking compatibility doesn't use a license slot; only adopting a device does.

How Buttons decides what's supported#

Every surface Buttons can drive (hardware panel, iPad, browser view, or third-party integration) comes from a model it ships a driver for. That set of models isn't fixed: it grows as Bitfocus builds support for new hardware, so a device that isn't supported today can become supported in a later release. Because of that, the definitive list lives in two places in the product itself rather than in a document that would drift out of date:
  • The Add surface dialog, for models you create directly (such as an iPad Mini, a Custom Web View, or a USB Relay), grouped by manufacturer.
  • The Discovered surfaces list, for hardware and third-party devices Buttons finds automatically on the network or over USB and matches to a model by its identifiers.
A device Buttons can see but doesn't have a driver for isn't hidden: it's shown with a clear Not supported indicator, so you know it was detected rather than missed.

Check a device you've already connected#

  1. Open Connect → Surface.
  2. Select Discovered surfaces.
  3. Find the panel by its hostname, network address, serial number, or detected model.
Each row shows what Buttons detected. A supported device can be selected and adopted normally, see Discover and adopt a hardware surface. An unsupported one carries a red Not supported badge and, next to its detected model name, Cannot be adopted. Hovering the row shows "This device is not supported by Buttons."

Note

If you select several discovered devices at once and any of them are unsupported, both Adopt and Adopt → Create Position stay disabled (with a tooltip stating how many selected devices can't be adopted) until you deselect the unsupported ones. There's no way to force-adopt an unsupported device or assign it a different model as a substitute.

Check a model before you connect it#

For surfaces you add rather than discover (an iPad Mini, a Custom Web View, or a USB Relay), open Connect → Surface → Add and look through the models grouped by manufacturer (for example, Buttons, Apple, and Elgato, with more added over time). If a model doesn't appear there and doesn't show up in Discovered surfaces once connected, treat it as unsupported for this release.

If you need an answer before you have Buttons running#

If you're planning a purchase or an installation before you have access to a running Buttons system to check yourself, confirm compatibility with Bitfocus directly rather than guessing from a panel's age or spec sheet: the supported-model set is a product decision that changes between releases.

If you get stuck#

What you see
What to try
The discovered panel says Not supported.
Don't adopt it as a different model: that isn't possible. Check Add for the current list of models you can create directly, or confirm compatibility with Bitfocus.
A mixed selection of discovered devices won't adopt.
Deselect any device marked Not supported: bulk adoption is blocked while even one selected device can't be adopted.
A panel you expected to see isn't in Discovered surfaces at all.
Confirm it's powered, connected, and reachable before assuming it's unsupported, see the discovery troubleshooting in Add and attach a surface.

Where to go next#

  • Add and attach a surface, to adopt a supported device or create an iPad, Custom Web View, or USB Relay surface.
  • Set device orientation and verify button placement, once a supported panel is adopted and mounted.

Was this helpful?

Was this helpful?

0 of 0 users found this page helpful