Limitations

External video

If the document embeds YouTube or Vimeo video, that media still depends on the external service and does not become part of the HTML file. It usually works when the documentation is served over http or https, but it may fail in a local file opened directly from disk.

If local usability matters, a better option is to show an image preview and open the actual video on YouTube in a new tab. That approach is more reliable both in the hosted version and in a file opened directly on the user's computer.

External scripts and analytics counters

Integrations such as Google Analytics, Yandex Metrica, and Webvisor load from third-party domains. In a local HTML file, these integrations may fail to load, work only partially, or stop sending events. Full analytics should be treated as a hosted-only capability.

Internet-dependent widgets

Any external iframe, support chat, third-party form, or embedded widget depends on external code loading. Offline, these blocks may fail to open, render as empty areas, or break the intended page flow. Important areas should have fallback text, a direct link, or static replacement content.

Local files and browser policy

Browsers restrict part of the behavior available to HTML files opened directly through file://. Because of that, some external connections, embedded services, and network-dependent scenarios behave worse than on a normal hosted site. The final document should be tested in both modes: as a local file and as a published page on a server.

Offline mode is not universal

Document structure, navigation, embedded styles, scripts, and images can work offline, but not every content type is equally self-contained. Text documentation, instructions, embedded images, and most local logic usually remain available, while external media and services may require internet access and hosting.

If the document must open reliably without a network connection, favor text, images, and embedded elements, and treat external dependencies as optional enhancements.