On this page
Customizing Control Bar Buttons
Overview
The Control Bar is divided into two sections:
- Left (File-level): Integration with external applications and quick actions (e.g., "Open with...", "Reveal in File Explorer"). These are configurable in
Settings > Controls. - Right (Preview-level): Viewport controls (e.g., rotate, mute, zoom).
This guide focuses on extending the Left section.
Adding Controls
In Settings > Controls, you can manage built-in buttons, create custom actions, or install control plugins.
1. Custom Actions
- Click + below the actions list and select the program or script to run.
- Configure the action details on the right panel:
- Name: Display name shown in tooltips.
- Executable: Path to the target executable (
.exe). - Arguments: Command-line arguments. Use placeholders like
"${input_file}"to pass file paths. - File Formats: Target file extensions (e.g.,
png,zip) or Special Tokens (e.g.,${type_folder}). - Close preview after successful launch: Close the preview once the external program starts successfully. Seer does not wait for the program to finish.
2. Control Plugins
Control plugins supply packaged actions. They are separate from custom actions, which use a program or script you already have.
Official Control Plugins
Official control plugin packages are available in the download center. Please visit Plugin Downloads - Controls to download the .zip packages. Downloaded archives can be imported directly in Settings > Controls without extracting.
Install the Download
- In
Settings > Controls, click + below the list. - Select the downloaded
.zipdirectly, or selectplugin.jsonfrom a complete extracted package. - Review the imported action's formats and behavior in the details panel.
- Click Okay to save and use it. Cancel discards the import.
If a package provides a different capability, Seer takes you to the corresponding settings page.
Managing Actions
- Reorder: Drag and drop items in the list to rearrange button order on the Control Bar.
- Toggle: Select an action and change Enabled in its details, then save settings.
- Customize Overrides: For installed plugins, you can customize the matched file formats and CLI arguments, or reset them to default anytime.
- Built-in Buttons: Built-in actions (Open with Default Application, Reveal in File Explorer, Same-Type Navigation) can be toggled individually.
Placeholders and Arguments
When configuring custom actions or control plugins, you can use placeholders in the command-line arguments to dynamically pass information about the currently previewed target:
- Common Placeholders:
"${input_file}": Absolute path of the previewed file or folder (if the path may contain spaces, always wrap it in double quotes).${7z}: Absolute path to the bundled7z.exe(can also be entered directly in the Executable field).
- File Format Special Tokens: In the File Formats field, in addition to standard file extensions (e.g.
png, zip), you can match broad categories:${type_folder}: Matches directories and folders;${type_file}: Matches all files;${type_all}: Matches both files and folders.
Complete Placeholders & Capability-Specific Rules: Different plugin capabilities support different sets of placeholders (for example, Control plugins only receive read-only input paths and cannot use output directory tokens; Property plugins require output paths).
Visit the official reference guide for the complete specification:
- 📖 Control Plugin Placeholders
- 🌐 Universal Placeholders (including ${seer_exe}, ${theme}, ${lang}, ${screenshot}, etc.)
- 🏷️ File Format Matcher Tokens (${type_*})
3. Configuration Example: Extract Archive with 7-Zip
To add a button that extracts archives using the bundled 7-Zip:
- Executable:
${7z}(or browse to your own7z.exe). - Arguments:
x "${input_file}" -r -y -o"C:\Output\Path\" - File Formats:
zip rar 7z tar gz
Parameter Breakdown:
* x: Extract with full paths.
* "${input_file}": Target archive file.
* -r: Recurse into subdirectories.
* -y: Assume Yes on all queries (overwrite).
* -o"...": Output directory.