Mac detects the external monitor but shows no signal: what to check

If your Mac lists an external monitor but the panel says no signal, start at the monitor. Select the port that actually carries the Mac, connect directly while testing a dock, and choose a conservative resolution and refresh rate. A display appearing in System Settings proves detection. It does not prove that the right input is selected or that a stable picture reached the panel.

Use the same standard for sound. A selected output or saved app route is a request. The proof is a recognizable sound coming from the intended device and nowhere else.

Disclosure: I build TeenyApps, including TeenyDisplay and TeenySound. Their source informed the limits described here. Apple's controls and the monitor's physical menu remain the safer first tests.

Find the failed layer before changing another setting

01Prove detection and the cable path

Check that the Mac supports the number and resolution of displays you connected. Then simplify the path. Wake the display, reseat both ends of the cable, and connect the monitor directly to the Mac if a dock or hub sits between them.

Apple says macOS should detect a properly connected display automatically. In Displays settings, hold Option to reveal Detect Displays if needed. Apple's current troubleshooting also recommends checking cable and adapter capability, allowing the accessory when macOS asks, and installing available software or display firmware updates.

Record the display name, resolution, and refresh rate before adding the dock again. If the direct connection works and the docked path does not, you have a useful comparison. Do not hide that difference with a preset.

02Prove the monitor is listening to the Mac's port

A detected display can still show no signal when its physical input points elsewhere. Open the monitor's own input menu and match the port label to the connected cable. If the Mac uses DisplayPort 1, choosing DisplayPort 2 is still wrong even though both labels sound close.

DDC input switching adds another failure mode: sending a value is not the same as observing the monitor accept it. Some monitors use vendor-specific values, and changing away from the Mac can remove the very DDC connection needed to switch back.

Before automating a switch, keep the monitor buttons or remote reachable, confirm both source devices are awake, and write down the known-good return input. The detailed Mac monitor input switching guide covers the safe test and current TeenyDisplay limits.

03Prove a stable picture before adjusting color or brightness

Once the right input shows an image, choose a resolution and refresh rate the Mac and display both support. Watch for intermittent blanking, scaled text that is hard to read, or a panel warning about an unsupported mode. A screenshot cannot prove the panel itself looks right.

Next check the active color profile and the monitor's picture mode. Only then adjust brightness or contrast. Many third-party monitors require their physical controls or DDC/CI for hardware brightness because macOS does not expose the same control it offers for a built-in display.

TeenyDisplay can expose supported DDC controls and display details from the menu bar. Its controls cannot repair an unstable cable, add DDC support to a monitor, or prove a picture without a visible check.

04Prove the system audio output

HDMI, DisplayPort, and USB-C displays can add an audio destination. Open System Settings, Sound, Output & Input and select the device you want. Then play a short, recognizable sound. Confirm it comes from the intended speakers or headphones and not from the monitor or MacBook.

Apple notes that an app's volume cannot exceed the output volume set in Sound settings. If the named device is selected but silent, check its hardware volume, mute state, connection, and the app's own audio selector before adding per-app routing.

For the same sound on multiple devices, Apple's Audio MIDI Setup can create a Multi-Output Device. That sends the same system mix to several outputs. It does not assign one app to speakers and another to headphones.

05Prove each app route while the app is playing

Per-app routing comes last. Start the app and play identifiable audio before selecting a custom output. Verify the named device is still connected, then listen at every output that should and should not receive the app.

TeenySound can route an active app to selected devices and remember the selection by app. Its current source creates one route for each selected device, so choosing two outputs duplicates the app stream to both. It does not split channels or different content between them.

The source also falls back to the current default output when a saved custom device can no longer be resolved. That prevents a dead route, but it means the saved choice alone is not proof. Use the per-app audio routing acceptance test after a display, dock, or Bluetooth device reconnects.

A short acceptance record for repeatable desk fixes

For a desk that fails more than once, write down the result instead of trusting the control you clicked.

1. Record the cable, dock port, and physical monitor input.
2. Record the display name, resolution, and refresh rate shown by macOS.
3. Describe the picture that proves the intended source is visible.
4. Record the system output name and the sound used to test it.
5. For a custom app route, record the app, selected outputs, and what you heard.
6. Keep one recovery path: a direct cable, monitor button, remote, or known-good input value.

For the shorter reconnect version, use the Mac docked desk reset for display and audio. It applies the same order to a desk that worked before.

When a utility helps and when it does not

Sources checked

• TeenyDisplay behavior was checked against the TeenyDisplay homepage and current local Swift source for DDC input commands, visible input choices, and failure handling.
• TeenySound behavior was checked against the TeenySound homepage and current local Swift source for app routes, multiple outputs, missing-device fallback, and device-specific volume memory.
• Apple Mac User Guide: Connect one or more external displays with your Mac.
• Apple Support: If your external display is dark or low resolution.
• Apple Support: Change the sound output settings on Mac.
• Apple Audio MIDI Setup User Guide: Play audio through multiple devices at once.

FAQ

Why does my Mac detect a monitor that still says no signal?

Detection only proves that the Mac and display exchanged some connection data. The monitor can still be on the wrong physical input, reject the selected mode, or have a cable or dock path that does not carry a stable picture.

How do I prove a monitor input switch worked?

Confirm the target computer or device is connected and showing a distinctive picture, issue the switch while the monitor controls remain reachable, and verify that exact picture appears. A sent command or changed app control is not enough.

How do I know Mac audio is using the intended output?

Select the device in Sound settings, play a recognizable sound, and confirm it is audible only from the intended speakers or headphones. Then test any per-app route separately.