Give one profile one purpose
A named mpv profile groups configuration options for a deliberate purpose. Define the task before writing one: a review window, a known display arrangement or a small comparison of settings. Avoid importing a large configuration merely because its label sounds appropriate. The options it changes matter more than the name.
Record the installed mpv version and preserve the existing configuration. List the intended options and why each belongs in the profile. Keep unrelated changes out of the first draft. This guide is for locally controlled playback of media you may use, and it does not supply service access, stream credentials or a promise that a profile improves every file.
Inspect the selected profile before playback
A named configuration section starts with a header such as [review-window], followed by its options. List available profiles with --profile=help, inspect one with --show-profile=review-window, and select it at launch with --profile=review-window. Use the documented help and show-profile facilities available in your release to check the resolved contents. A profile can include other profiles, so the short visible section is not always the complete set of effective changes.
Apply the small profile at launch to an owned sample and review only the intended effects. Keep the baseline launch arrangement available. If the result is different from the expectation, inspect which options were supplied rather than adding compensating settings until the picture happens to look acceptable. Record any actual local observations with their version; no playback test was performed for this guide.
Treat runtime application as a state change
The mpv documentation explains that applying a profile during playback overwrites option values. It is not automatically a reversible enable/disable switch. Decide whether runtime use is needed, then choose a documented restore policy where appropriate and write what state should be recovered.
Pay particular attention to list-valued settings such as filters. A saved list restored later is a snapshot, not necessarily an inverse operation that removes only the profile's own addition. If another adjustment occurs after the profile was applied, decide whether preserving that later adjustment matters. A clear policy prevents the word restore from promising more than the implementation provides.
Review a complete apply-and-return cycle
Use a small local acceptance sequence: capture the baseline values, apply the profile, inspect the intended changes, make only the permitted subsequent adjustment, then restore according to the chosen policy. Compare the final values with the expectation. Keep this exercise away from a live presentation until its consequences are understood.
Document the profile purpose, included options, launch route and runtime policy alongside the configuration. Recheck it after upgrading mpv or changing a nested profile. Completion means you can explain both the active state and the route back to the intended baseline, rather than relying on a collection of undocumented toggles or claims that somebody else's settings are universally optimal.
Questions answered
Is apply-profile automatically a toggle?
No. Runtime application changes option values; restoration needs an explicit supported policy and an understood baseline.
Does restoring a filter profile always remove only its own filter?
Do not assume that. The documentation describes saved-value restoration, including whole list values.
Sources & further reading
Official references for the subjects discussed. Service terms and device software can change.