Start your 3-day free trial
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.


When a streaming app has sound but no picture, the audio is still reaching you, so the fault usually sits on the video side of the device or in the cable path: the video layer, decoder, display mode, or HDMI chain.[1] First decide whether the app interface remains visible and whether the fault affects one title, one app, one device, or the entire external display.
Key Takeaways
- “Sound but no picture” is different from a television with no signal and no audio.
- One affected title suggests a content or service report; every title suggests the app or device.
- If the picture fails only on an external display, test a direct HDMI path before resetting software.
- Change one port, cable, client, or display condition at a time.
- App resets and factory resets can remove sign-ins, downloads, and settings, so they come last.
The streaming buffering workflow covers pauses and insufficient delivery. This guide is for a different symptom: audio continues, but the expected video is black, blank, or missing.
Observe the screen before touching settings:
| What you can still see | First branch | Why it matters |
|---|---|---|
| App menus, subtitles, or playback controls | Title, app video layer, decoder | The display still receives a picture |
| TV menus but no device image | HDMI input, cable, receiver, output mode | The television works but the source path does not |
| Nothing from the source, including menus | Power, input, HDMI signal, source device | This is wider than one streaming app |
| Video works on the built-in screen, not the TV | Adapter, HDCP, cable, receiver, display mode | The app can decode locally |
Netflix describes black screen with sound as commonly involving the device or a video cable, and separates it from cases with neither sound nor video.[1] Preserve that distinction. A television with the wrong input or an unpowered streaming stick needs a signal-path check, not an app cache reset.
Also note whether subtitles and controls appear over the black area. Visible controls indicate that the app is drawing its interface while the protected video plane or decoder output is failing. That clue narrows the investigation without claiming a specific cause.
Begin with two small comparisons:
Use the results as a matrix:
Netflix's current mobile guidance explicitly asks whether other programs work and provides a title-reporting route when they do.[1] That is a better first response than reinstalling an app for a single damaged or misconfigured title.
Record the title, time position, audio language, subtitle state, and whether previews or trailers work. If the failure always begins at the same timestamp on one title, the service has stronger evidence than a generic “black screen” report.
Restart in increasing order of disruption:
Do not merely switch the television to standby if the manufacturer requires a full restart. Netflix's TV-device guidance recommends disconnecting power, waiting, reconnecting, and testing again.[1] Google likewise distinguishes unplugging a streaming device's power cable from removing only HDMI.[2]
If the picture returns, note which component was restarted and whether the fault recurs after sleep, resolution switching, or opening another app. A repeatable trigger is more useful than a one-time recovery.
Use official update channels. Do not install random codec packs or disable browser security features to make protected video render.
For an app or browser branch:
Netflix currently recommends browser updates for computer playback and current video drivers on Windows when video is missing.[1] Follow the computer or GPU manufacturer's instructions; do not treat a third-party driver downloader as authoritative.
If one supported browser works and another does not, keep the display and title fixed and compare hardware acceleration only when the browser or service documentation identifies it as a troubleshooting step. Changing acceleration, extensions, DRM settings, and drivers together destroys the comparison.
If audio and video travel through a television, monitor, dock, adapter, AV receiver, soundbar, or HDMI switch, build the shortest supported path:
Netflix recommends direct connection when receivers or sound systems are present, then another HDMI port and cable.[1] Google similarly recommends direct television connection when an HDMI switch, AVR, or soundbar is involved in an HDCP error.[2] Apple advises direct connection to isolate an HDMI switch or AV receiver.[3]
Change one item per test. Swapping the port, cable, receiver, and resolution simultaneously may restore the picture but leave the faulty component unknown.
Do not assume that hearing audio proves the entire HDMI handshake succeeded. Audio and video capabilities can be negotiated separately, while protected video may require a compatible path. Use the service and device maker's supported-connection guidance instead of bypass hardware or tools intended to defeat copy protection.
For a casting session that fails only when network routing changes, use the separate casting connection guide. This article stays focused on a video output that is absent while audio continues.
An external display can go blank when the source switches to a format the chain does not handle reliably. Keep the test conservative:
Apple notes that Apple TV can show a blank or flickering screen while switching formats when Match Dynamic Range or Match Frame Rate is enabled. Its support flow also offers a resolution-switching procedure and checks the HDMI cable, input, port, switch, and receiver.[3] This is an Apple TV example, not a universal menu path.
Avoid forcing 4K, HDR, a high refresh rate, or deep color merely because each component advertises it separately. The complete path—including source, cable, switch or receiver, port, and display—must support the chosen combination.
This article does not expand into HDR color diagnosis. If standard dynamic range works but HDR alone fails, preserve that result for the device maker or a dedicated HDR workflow rather than changing unrelated streaming settings.
If the device displays an HDMI or HDCP error, use that exact branch in the official support documentation. Google recommends rebooting the source and display chain, reseating the connection, trying another input, and connecting directly when an AVR or soundbar is involved.[2]
Do not use an HDCP bypass device or screen-capture workaround. Those paths can violate service terms, reduce security, and create a new compatibility layer. The diagnostic goal is to restore a supported end-to-end connection.
For phone or tablet adapters, confirm that the streaming service supports that connection and that the adapter and cable meet the documented requirements. A generic adapter that mirrors the home screen may still be unsupported for protected playback.
If the error follows one adapter or receiver across displays, contact that manufacturer. If it follows the streaming source even when directly connected with a known-compatible cable, contact the source-device or service support team with the recorded matrix.
An app reset can sign you out. Reinstalling can remove downloads. A device factory reset can remove Wi-Fi, accounts, apps, display preferences, and accessibility settings.
Before any reset:
Google labels factory reset as the last step and warns that it clears data and cannot be undone.[2] Netflix warns that some device restore procedures can remove apps, data, or settings.[1] These consequences are why a reset is not a sensible first response to one affected title.
Send support a compact record:
Exclude passwords, account recovery codes, and personal viewing details that are not necessary for the report. The matrix should identify the smallest failing combination.
The audio path can continue while the video layer, decoder, protected output, or display format fails. Check whether the app interface remains visible and whether the fault follows one title, app, device, or HDMI path.
Restart the smallest affected component first: app, then source device, then the display chain. Follow the manufacturer's power-cycle instructions and retest the same title after each change.
Yes. Video format or protected-content negotiation can fail even when audio continues. Reseat the cable, bypass receivers, and test one known-compatible cable and port.
A title-specific fault or service-side media problem is more likely when other programs work in the same app and device. Report the title and timestamp rather than resetting the whole device.
The external path adds output resolution, adapter, cable, receiver, HDMI input, display processing, and protection requirements. Test a supported direct connection at a conservative display mode.
Only use that comparison when the browser or service's official guidance recommends it. First update the supported browser and graphics driver, and change one variable at a time.
No. A VPN does not repair a decoder, HDMI cable, HDCP path, graphics driver, or display mode. Diagnose the video and display chain directly; the streaming VPN decision guide explains which parts of a viewing setup a VPN does change.
Only after title, app, update, direct-connection, cable, port, and supported display-mode tests fail and the manufacturer recommends it. Confirm what the reset erases and that you can recover the account first.
Sources checked 4 October 2026.
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.