macOS camera support: permissions, USB microscopes, endoscopes, and UVC cameras

If you need macOS camera support for a USB microscope, endoscope, otoscope-style camera, or UVC inspection camera, the first answer is practical: confirm camera permission, confirm the source type, and confirm whether macOS exposes the device as a standard camera. ScopeDock can work with compatible local camera paths, but it should not be treated as a universal driver for every vendor-specific device.

This guide is about setup and compatibility boundaries. It is not medical advice, and ScopeDock should not be used as a medical diagnostic tool.

Start with what kind of source you are using

Before assuming the product is broken, identify whether the device is one of these paths:

• a USB UVC camera
• a USB microscope or endoscope that appears to macOS as a camera
• an RTSP source
• an ONVIF-discovered network device
• a vendor-private camera that only works in the manufacturer’s app

Those paths do not fail in the same way, so support guidance should not treat them as one generic “camera problem.”

Quick macOS camera permission checks

For local camera workflows, permission state is often the fastest thing to verify. If macOS has not granted camera access, ScopeDock may look like it cannot see the device even when the physical connection is fine.

Check these items first:

1. Open macOS System Settings and confirm camera permission for ScopeDock.
2. Quit and reopen ScopeDock after changing permission.
3. Disconnect and reconnect the USB camera or adapter.
4. Close other camera apps that may already be using the device.
5. Test one camera source before adding more sources.

If the device appears in other standard Mac camera apps but not in ScopeDock, treat that as a useful compatibility detail when you send feedback.

USB microscope and endoscope support boundary

USB microscopes and endoscope cameras usually work best on macOS when they expose a standard USB UVC camera path. In that case, macOS can present the device to apps without a custom vendor driver.

Compatibility is less predictable when:

• the device requires a vendor-only app
• the device uses a private USB protocol
• the camera appears as storage, serial hardware, or another non-camera device
• an adapter, hub, or cable prevents stable video transfer
• the product is marketed as an otoscope or medical camera but does not expose a normal camera stream

If your workflow is specifically USB microscope or endoscope review, also read USB microscope and endoscope camera software for macOS before downloading.

UVC camera support is not the same as every USB camera

UVC is a useful compatibility signal because it means the device behaves like a standard USB video camera. But “USB camera” is broader than “USB UVC camera.” Some USB devices need private drivers or only expose video inside a vendor app.

ScopeDock should be evaluated against the source path macOS can actually see:

Device behavior	What it usually means
macOS exposes it as a camera	Start with permission checks and one-source preview.
Only the vendor app sees video	ScopeDock compatibility may be limited by a private protocol.
The camera appears but preview is blank	Re-check permission, cable, adapter, another app locking the device, and source selection.
The device is actually RTSP or ONVIF	Use network-camera troubleshooting instead of USB permission troubleshooting.

For platform, architecture, and source coverage, use Download and Compatibility before installing.

When ScopeDock can help

ScopeDock is a better fit when your camera source is available to macOS as a standard local camera path or reachable network stream, and your goal is local preview, inspection, snapshots, or short recordings.

ScopeDock is not positioned as:

• a replacement for a vendor’s private USB driver
• a medical diagnosis platform
• a guarantee that every microscope, endoscope, or otoscope-branded device will work
• a surveillance wall or NVR system

If the device path is unclear, start with Support and the compatibility feedback lane before assuming the product or device is broken.

What to include if you contact support

Support becomes much faster when the report includes enough context to separate permission, UVC compatibility, and product behavior:

• Mac model or chip
• macOS version
• ScopeDock version
• source type: USB UVC, USB microscope, endoscope, otoscope, RTSP, or ONVIF
• camera family or model if you can share it
• expected behavior
• what the app currently does instead
• whether the camera appears in another standard Mac camera app

Do not send medical media, passwords, private LAN details, full RTSP URLs, or sensitive file paths. Use Contact / Feedback when the documented path still does not match your device.

FAQ

Why does my USB microscope not open on macOS?

The most common causes are missing camera permission, another app using the camera, an adapter or cable issue, or a device that does not expose a standard USB UVC camera path. Start with permission and one-source testing, then compare the device against the USB microscope guide.

Does macOS support every endoscope camera?

No. macOS support depends on how the camera presents itself. Endoscope-style devices that appear as standard UVC cameras are easier to evaluate. Devices that only work through a vendor app may use private protocols that ScopeDock cannot treat as a normal camera input.

What is a UVC camera?

A UVC camera follows the USB Video Class pattern, which lets macOS expose the device as a camera source without a custom vendor app. It is a useful compatibility signal, but it still does not guarantee every device behavior or capture mode.

Is this page for medical camera diagnosis?

No. This page explains camera permission and compatibility troubleshooting for local preview and inspection workflows. ScopeDock is not a medical diagnostic product.

Where should I go if the camera still does not work?

Use Support for troubleshooting lanes, Download and Compatibility for platform and source checks, or Contact / Feedback if you can share device behavior without private or sensitive details.