DictaFlow
DictaFlow Blog

Signal Screenshots Blocked in 2026: Write a Bug Report

A useful support ticket can start with a made-up sentence, not a private chat capture.

November 20, 2026

Editorial illustration of a shielded phone, microphone, and blank support-report sheet
Original editorial illustration, not a Signal interface or a compatibility-test screenshot.

If Signal screenshots are blocked, keep Screen security on while you write the first bug report. Use made-up message text to describe what you did and what happened. Give support steps to try without sharing the private conversation. In its November 20 announcement, Signal said it was expanding screenshot restrictions on phones to limit AI agents' ability to read chats.[1]

If you're trying to report a typing problem, a blank capture may look like another broken feature. It could mean the protection is working, though. Signal's Windows guidance says Signal Desktop blocks screenshots by default on Windows 11. The setting is under Settings > Privacy > Screen security.[3] Signal mentioned this Windows setting before today's news.

Reuters reports on the new mobile restrictions and Signal's warning that protection remains incomplete.[10] The report follows the dispute over agents reading private messages. But suppose your immediate problem is a broken writing tool and support asks for a screenshot. Giving a second service the conversation would expand the problem you're trying to report.

What changed today, and what a blank screenshot proves

Signal says its new protections cover iOS 27 and Android when it can detect an AI assistant trying to read the screen. Android coverage varies. Signal also says it can't reliably offer the same screenshot protection on macOS.[1] A headline about phones doesn't mean every desktop or Android device is covered.

A blank screenshot proves little. You tried to capture the Signal window and got nothing useful. It doesn't prove that no other tool can get the content. Signal specifically warns that other ways to access it may exist, including files already on the device.[1]

When you contact support, describe only what you saw. Write "the capture showed a blank Signal window," rather than "Signal deleted my message" or "the dictation app was blocked." A screenshot failure gives you no diagnosis of the dictation fault. It leaves open whether recognition failed, the words landed elsewhere, or the message never sent.

I wouldn't disable a protection just to make the first support ticket seem more convincing. Write down how to reproduce the problem and include the details an engineer needs. If support can't reproduce it, discuss what other evidence might help.

Replace the conversation with a disposable test

Use a destination you control for testing, and make up the content. Don't test in a real client's conversation. If you need someone else to take part, agree on a harmless test first. Keep the text short so you can check it without taking a screenshot.

For example, dictate: "The blue folder stays here until Friday." This sentence is made up for testing. Write down the actual result separately. A missing word, a repeated sentence, and no inserted text each give you a different clue. Keep any odd result exactly as it appears, even if it looks silly.

Check the cursor first. Click the message box before you start. Note whether the text showed up there, in another window, or nowhere you could see. Record whether you stopped before sending. This helps prevent a text-entry test from accidentally sending someone a message.

If the same input still fails, dictate the sentence into a blank note outside Signal. Dictate it again. Typing would skip the speech step you need to compare. Keep the microphone and dictation settings the same for both.

If the note test works, check the destination or insertion path next. That still doesn't prove Signal caused the problem. If both tests fail, let support know. These are suggested troubleshooting steps, not results from hands-on compatibility tests in this article.

You may not need to send a message during the test. If the fault happens before you press Send, stop and describe what happened. Leave the draft unsent. If sending causes a delivery problem, tell support and ask how to reproduce it without sharing the original exchange.

Write a report that survives without a screenshot

A short ticket can still give someone enough information to reproduce the issue. Include your operating system and version, Signal version, and dictation tool version. Say how you started dictation: with keyboard dictation, an app's hold-to-talk shortcut, or an agent asked to compose a reply.

Here is a blank report outline. Fill it with observations from your test.

  • Action: Clicked the Signal message box and dictated the test sentence.
  • Expected: The unsent draft should contain the spoken sentence once.
  • Actual: Record exactly what appeared, including any missing words.
  • Comparison: State what happened when the same sentence was dictated into a blank note.
  • Capture: Explain that Screen security stayed enabled and the screenshot was blank.

Only say a comparison passed if you've tried it. Write "not tested" for a comparison you haven't tried. Support can ask you to do it later.

If the fault comes and goes, note when it happens and your time zone. Support can ask about one specific attempt instead of grouping separate failures together. Copy an error message only if it contains no private information, and check it before sending. Review the diagnostic logs too. A file called "logs" may still contain details you didn't mean to share.

Keep the ticket in a note until you know where to send it. A public issue tracker and a private support address reach different people. Describe the failure publicly, and share device-specific details only with the support channel that needs them.

Accessibility needs deserve a separate conversation

In an earlier Windows announcement, Signal said screenshot blocking could affect some screen readers and magnification tools.[4] That can make the app harder to use. People who rely on those tools may face a different choice than someone who just wants a screenshot for a ticket.

When you contact Signal support, tell them which accessibility feature you use and what you can't do without it. Ask which options your device supports. Advice about a desktop magnifier may not help with phone dictation. The announcement concerns AI agents using device access. It does not establish how your particular assistive tool works.

You don't have to stop using voice input just because support asks for pictures. Ask whether a written description of the problem is enough. If they need an image, first agree on a test conversation with made-up content. Then discuss whether a settings change is necessary. Signal's help page says the setting applies to your device, not screenshots taken by another participant.[3]

Where voice input can help with the ticket

I build DictaFlow, so I have a commercial connection to it. Its desktop hold-to-talk feature can help you write a report in a supported text field.[5] You can also use your current dictation tool or type the ticket. We have not tested these options against a protected Signal window for this article.

Start with a blank note and dictate what you noticed. Then read your notes back. Keep "the screenshot was blank" separate from "the message composer stayed empty." They describe different failures, so an automatic rewrite shouldn't treat them as one diagnosis.

Before sending it, remove any real names or conversation excerpts from the draft. Include the made-up sentence, the actual result, and the versions you recorded. Leave Screen security unchanged while support reviews the first report.

Sources

[1] Signal >> Blog >> Signal is Serious About Protecting Your Privacy

[3] Signal Support: Screen Security

[4] Signal >> Blog >> By Default, Signal Doesn't Recall

[5] DictaFlow - AI Dictation for Windows, Mac, iPhone & Android

[10] Reuters via TimesLIVE: Signal restricts screenshots, November 20