Start with a clean baseline
Separate enumeration, permission, actual video frames, active resolution/frame rate and source/capture format. 'Detected' is not the same as 'working correctly.'
Live evidence
Relevant checks
Device & Browser Information CheckSee browser-exposed screen, viewport, language, CPU-thread class, memory class, connection hints, and platform information without installing software.
→Browser Permission CheckCheck whether common browser permissions such as camera, microphone, location, and notifications are granted, denied, or still waiting for a decision.
→First sequence
Do the high-signal checks before risky changes
- 1
Confirm the scanner appears in the operating system
- 2
Test the manufacturer's scan utility
- 3
Separate scan-hardware failure from browser upload/viewer issues
Decision points
What the result should change
If live preview worksPrioritize the affected meeting/streaming app, selected source, virtual camera or profile.
If video works only at a lower modePrioritize cable/USB bandwidth, hub/dock topology or unsupported source mode.
If no frames arrive anywhereSimplify to direct connection, OS recognition and official firmware/driver guidance.
Browser can help check
- Check whether web scanning apps have browser permissions
- Help diagnose file/upload/browser issues around scanning
Browser cannot prove
- Drive generic scanner hardware directly across browsers
- Test scanner lamps, motors or ADF sensors
Repair boundary
Know when to stop browser troubleshooting
- A browser cannot diagnose image-sensor electronics or lens alignment.
- Capture cards can be limited by HDMI format/HDCP/EDID even when USB enumeration succeeds.
- Do not install unsigned camera/capture drivers from download aggregators.
Used-device inspection
What to verify before paying or signing off a repair
- Verify the exact resolution/FPS modes you need
- Test microphone if integrated
- For capture devices, verify passthrough and capture are separate specifications