# Replace missing embedded dashboards with a readable snapshot

Canonical: https://githtml.com/guides/iframe-content-missing-html-report
Published: 2026-09-26
Publisher: WaveTech LLC / gitHtml

Treat an iframe as a separate document with its own network, authorization, and embedding requirements. If it is missing, obtain a static summary or approved snapshot during authoring. Include the key values, filters, and capture time in HTML text so the report does not depend on a live dashboard to communicate its result.

## Recognize the separate document boundary

An iframe is not the same as an image or a paragraph copied into your report. It loads another page, which may need scripts, authentication, cookies, or permissions to function. The destination may also refuse embedding. A blank frame therefore has several possible causes, and enabling one setting may not address the actual problem.

Start by identifying the frame's destination and intended purpose. Is it evidence for a decision, an optional interactive exploration, or merely a decorative preview? The answer determines the repair. Essential evidence needs a dependable representation in the report itself. Optional exploration can remain a clearly labeled external destination without occupying an empty rectangle in the reading flow.

## Capture the meaning, not only the pixels

A screenshot can preserve appearance but may omit filters, date ranges, or hover-only values. Write the important context beside it. For a performance dashboard, include the metric definition, reporting window, relevant values, and the interpretation. If the data is a snapshot, say when it was captured and avoid presenting it as a live status.

Check confidentiality before copying dashboard material into a portable document. The dashboard's access controls do not automatically travel with a screenshot or static table. Publish only the fields appropriate for the report's audience. Where sensitive evidence must remain restricted, provide a non-sensitive summary and a clear reference to the authorized source.

## Make the report independent

In gitHtml, optional remote resources and JavaScript are off by default. A report containing essential iframe-only content is therefore not a dependable static reading artifact. Replace the dependency at export time and verify the result without loading the original dashboard. Keep a link for authorized readers who need deeper analysis, but do not make it the only place where the answer exists.

1. Identify the iframe destination and the question it is meant to answer.
2. Record selected filters and the data timestamp.
3. Write the key result and limitation directly in HTML.
4. Add an approved static visual only when it improves understanding.
5. Label the external dashboard as optional further exploration.
6. Remove empty frame placeholders from the portable version.

## Sources and further reading

- [MDN: iframe element](https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/iframe)

## Related guides

- [Find why an HTML document opens without its styling](https://githtml.com/guides/missing-css-in-html-reader)
- [Troubleshoot broken relative image paths in repository HTML](https://githtml.com/guides/broken-relative-image-paths-html)
- [Distinguish a GitHub file page from an image resource URL](https://githtml.com/guides/github-page-url-versus-image-resource)
- [Find the element making an HTML document scroll sideways](https://githtml.com/guides/html-document-horizontal-overflow)

Editorial approach: https://githtml.com/guides/about