# Fixing a report with no screenshot - Vynix

> Vynix report with no screenshot? Learn why captures get blocked by cross-origin content or policies, and how to fix and work around it.

[Help center](/kb/)

# Fixing a report with no screenshot

Updated July 31, 2026

If a Vynix report came through without a screenshot, the capture was usually blocked or interrupted. Here is how to work out why and what to do.

-   Check whether the page uses cross-origin content, such as embedded iframes or images from another domain, which can limit what a screenshot can capture.
-   Confirm the reporter did not navigate away or close the tab immediately after leaving the note, before the capture finished.
-   Look for a content security policy that could block the capture, and allow the values from the install screen if needed.
-   Ask the reporter which browser they used, since older or unusual browsers can affect capture.
-   Reproduce the issue yourself and leave a test note to see whether the screenshot attaches.

Even without a screenshot, the report still carries the element that was clicked, the page URL, the environment details and any captured console and network context, so it is rarely a dead end. You can often reproduce and fix the issue from those details alone.

Screenshots depend on what the browser will allow the page to capture. Cross-origin images and embedded content are the usual reasons a capture is partial or missing, because the browser protects content from other domains. This is a browser security behaviour rather than a fault in the report.

If reports on a specific page consistently come through without a screenshot, note which page and what it embeds, then contact support. A repeatable case is much easier to investigate than a one-off.

## Frequently asked questions

Why is there no screenshot on my report?

The capture was likely blocked by cross-origin content, a content security policy, or the tab closing before it finished. The rest of the report context is still available.

Can I still fix the issue without a screenshot?

Usually yes. The report still includes the clicked element, the URL, the environment, and any console and network context, which is often enough to reproduce the problem.

## Keep exploring Vynix

[Browse the full documentation](/docs/)[Explore every Vynix feature](/features/)

## Keep reading

[

### Controlling who can see the Vynix widget

Read](/kb/controlling-who-can-see-the-vynix-widget/)[

### Fixing a widget that does not appear

Read](/kb/fixing-a-widget-that-does-not-appear/)[

### How the Vynix AI diagnosis works

Read](/kb/how-the-vynix-ai-diagnosis-works/)

## Stop describing bugs. Point at them.

Add one script tag and give your AI agent the context it has been missing. Free while we grow.

[Get started free](/register)[Read the install guide](/install/)

---

Source: https://www.vynix.in/kb/fixing-a-report-with-no-screenshot/ | Markdown version for AI agents. Full site index: https://www.vynix.in/llms.txt