Mac display presets for external monitors: what gets saved

The direct answer: TeenyDisplay can save brightness, contrast, volume, input source, resolution, refresh rate, and HiDPI state for each connected display when those values are available. It does not save screen arrangement, mirror or extend mode, main-display choice, window positions, color profile, rotation, or Night Shift.

Save a preset only after the real display state passes. Then change one safe value, apply the preset, and inspect the physical monitor. A successful click or automation run is not proof that the audience, desk user, or room received the intended state.

This guide uses operational preset for a saved monitor-control state. Apple also uses preset for color reference modes on supported Apple displays. Those are different tools for different decisions.

What a TeenyDisplay preset covers

Separate Apple reference modes from operational presets

Apple's Displays settings own the Mac-side foundation: detection, arrangement, mirror or extend mode, resolution, brightness where available, color profile, rotation, refresh rate, and Night Shift.

On supported Apple displays, Apple also provides reference-mode presets for color workflows. A reference mode defines a color gamut, white point, luminance, and transfer function for work such as photography or video. It is not a saved room layout or a collection of third-party monitor controls.

A TeenyDisplay operational preset targets the repeated controls exposed by connected displays. Use the Apple path for the Mac-side display relationship and color target. Use the operational preset for the supported monitor state you want to restore.

What TeenyDisplay saves

The current preset source creates one entry for each connected display. That entry can contain brightness, contrast, volume, input source, resolution width and height, refresh rate, and whether the selected mode uses HiDPI. Unsupported or unavailable values are left out.

Preset records are stored locally through SwiftData. When you apply one, TeenyDisplay restores supported controls through the available paths: DDC for monitor controls, Core Audio for a matching display audio device, software brightness where used, and the selected Core Graphics display mode.

A mode is more than its resolution. The saved mode also includes refresh rate and HiDPI state, so the restore test should check readable size and refresh rate instead of looking only at pixel dimensions.

What stays outside the preset

TeenyDisplay's preset model has no fields for screen arrangement, mirror or extend mode, main-display choice, window positions, color profile, rotation, or Night Shift. Saving a preset cannot make those values part of it.

This boundary is useful during troubleshooting. If brightness and input restore but the presentation appears on the wrong screen, inspect macOS arrangement and main-display choice. If geometry is correct but color is wrong, inspect the color profile or reference mode.

For a stable desk, document the outside layer in the external-monitor workspace setup. For a live room, use the Mac presentation display settings checklist before saving any operational state.

How TeenyDisplay matches saved displays

A current display key includes vendor ID, product ID, and serial number when the monitor reports them. The preset manager also has a vendor-and-product fallback for older saved data that lacks the serial component.

This is more stable than a temporary display ID, but the result still depends on what the monitor and connection report. A disconnected display is skipped. A replaced or ambiguously identified monitor deserves a new acceptance test.

Name the preset for the operational context, such as "Workshop room A" or "Desk work," and keep the hardware path in the runbook when a particular dock, input, or cable matters.

Run a save, disturb, apply, verify test

1. Set macOS arrangement, mirror or extend mode, main display, color profile, and rotation first.
2. Set the connected displays to the required brightness, contrast, volume, input, resolution, refresh rate, and HiDPI state.
3. Inspect the physical desk or audience-facing result with representative content.
4. Open teenydisplay from the menu bar.
5. Save a named preset after the state passes.
6. Change one safe value, such as brightness, while monitor controls remain reachable.
7. Apply the preset and verify every required physical result, including readable scale and active input.
8. Test the manual fallback and record the macOS settings that stay outside the preset.

When the preset includes an input source, test that switch by itself first. The Mac external monitor input switching guide explains why you need reachable monitor controls if the selected input goes blank.

Treat default and automated presets as commands, not proof

TeenyDisplay can mark one preset as the default and apply it when the app launches. It can also apply a named preset through a teenydisplay:// URL command. The URL handler schedules preset application before printing its status line, so that line proves dispatch, not completed hardware writes. Both routes still depend on the displays that are connected and the controls they expose at that moment.

Test the named preset manually before making it the default or calling it from a launcher. After automation runs, verify the screen rather than the success of the trigger.

The current preset manager shows a warning if a save, rename, delete, or default-setting persistence operation fails. Treat that warning as a failed setup step. Do not continue as if the preset was stored.

When presets are the wrong tool

Skip the operational preset when only one setting changes. A keyboard brightness control or the monitor's own button may be clearer. Skip it while diagnosing color; use the Mac external monitor color profile checklist before saving the surrounding operational state.

Use a heavier display app if you need virtual displays, EDID overrides, custom scaling experiments, picture-in-picture, or full display layout protection. TeenyDisplay is intentionally narrower. It can switch available resolutions and refresh rates, but it is not trying to be a display engineering suite.

Use the monitor's own menu when a vendor-specific setting is not exposed through the control paths TeenyDisplay uses. A preset can restore only the values that were available to save and apply.

Common questions

Is an Apple display preset the same as a TeenyDisplay preset?

No. Apple's reference-mode presets on supported Apple displays define a color-workflow target. A TeenyDisplay preset stores operational values for connected displays, such as brightness, contrast, volume, input, resolution, refresh rate, and HiDPI state.

What does a TeenyDisplay preset save?

For each connected display, TeenyDisplay can save brightness, contrast, volume, input source, resolution width and height, refresh rate, and HiDPI state when those values are available.

What does a TeenyDisplay preset not save?

It does not save screen arrangement, mirror or extend mode, main-display choice, window positions, color profile, rotation, or Night Shift. Record those settings separately when they matter.

What happens when a preset display is disconnected?

TeenyDisplay matches saved entries to the displays currently connected and skips a saved display that is absent. Reconnect it and verify the full physical result before relying on the preset.

Sources checked

• TeenyDisplay claims were checked against the TeenyDisplay homepage and current local source for PresetManager and DisplayPreset, including saved fields, SwiftData persistence, display matching, application paths, and disconnected-display handling.
• Apple Support: Connect a display to your Mac for macOS display setup choices.
• Apple Support: Create custom reference modes on Mac for color gamut, white point, luminance, and transfer-function settings.
• Apple Support: Use reference modes with your Apple display for supported-display scope.