starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Add setting to control opacity when a screenshot or video capture is taken of the terminal area. #21358

New Issue
Closed
opened 2026-01-31 07:42:13 +00:00 by claunia · 1 comment
claunia commented 2026-01-31 07:42:13 +00:00
Owner
Copy Link

Originally created by @rkeithhill-keysight on GitHub (Mar 6, 2024).

Description of the new feature/enhancement

Add a new setting that controls background opacity while a screenshot or video capture is in progress. I typically would set opacity to 100% in this case, but others may prefer some sort of acrylic blur. With the setting configured this way, my terminal would NOT show anything behind it during a screenshot or video capture. After the screenshot (or video capture) completes, the opacity would return to normal.

I like having my terminal opacity set to 85%. This allows me to see items of import behind the terminal. I also share a lot of screenshots of my terminal to Teams and/or Slack. And sometimes, the items behind my terminal can be sensitive and I don't always realize what others can see bleeding through in these screenshots.

Proposed technical implementation details (optional)

TBH I'm not sure if an app can tell if a screenshot or video capture is underway. If it can, then it would be ideal to "automate" the opacity change to 100% and then back to the normal setting. If this can't be detected, then a keyboard shortcut to toggle between 100% opacity and the actual opacity setting would be OK.

I want a way to temporarily make my terminal 100% opaque during the recording process of a screenshot or video capture (like you can do now with the Windows 11 Snipping Tool).

Originally created by @rkeithhill-keysight on GitHub (Mar 6, 2024). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> # Description of the new feature/enhancement Add a new setting that controls background opacity while a screenshot or video capture is in progress. I typically would set opacity to 100% in this case, but others may prefer some sort of acrylic blur. With the setting configured this way, my terminal would NOT show anything behind it during a screenshot or video capture. After the screenshot (or video capture) completes, the opacity would return to normal. <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> I like having my terminal opacity set to 85%. This allows me to see items of import behind the terminal. I also share a lot of screenshots of my terminal to Teams and/or Slack. And sometimes, the items behind my terminal can be sensitive and I don't always realize what others can see bleeding through in these screenshots. # Proposed technical implementation details (optional) TBH I'm not sure if an app can tell if a screenshot or video capture is underway. If it can, then it would be ideal to "automate" the opacity change to 100% and then back to the normal setting. If this can't be detected, then a keyboard shortcut to toggle between 100% opacity and the actual opacity setting would be OK. <!-- A clear and concise description of what you want to happen. --> I want a way to temporarily make my terminal 100% opaque during the recording process of a screenshot or video capture (like you can do now with the Windows 11 Snipping Tool).
claunia added the Issue-FeatureNeeds-TriageNeeds-Tag-Fix labels 2026-01-31 07:42:14 +00:00
claunia commented 2026-01-31 07:42:15 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Mar 6, 2024):

Thanks for filing. We don't think there's a way to know if a screenshot/video capture is underway, like you said. However, you can probably use the adjustOpacity action to set your opacity quickly just before recording it.

@carlos-zamora commented on GitHub (Mar 6, 2024): Thanks for filing. We don't think there's a way to know if a screenshot/video capture is underway, like you said. However, you can probably use the [adjustOpacity action](https://learn.microsoft.com/en-us/windows/terminal/customize-settings/actions#adjust-opacity) to set your opacity quickly just before recording it.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Feature Needs-Tag-Fix Needs-Triage
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#21358
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?