A video’s preload value is a hint to the browser, not a promise that a request will start before playback. Even with preload="auto", the browser may choose differently; loading="lazy" defers preload behavior until the video is near or within the viewport, and autoplay takes precedence over preload. To verify delivery, record what the page requests at initial load, near the video, and after a visitor presses play, in each target browser and device.
Set an expectation you can verify
First confirm that the page uses an HTML <video> element. If it is a third-party embed or a custom player, its loading behavior may be controlled by that implementation rather than the attributes described here.
For native video, preload="none" signals that the author thinks no media should be preloaded; metadata asks for metadata such as duration; and auto says the whole file may be downloaded even when playback is not expected. These values describe intent, not guaranteed outcomes. The browser may ignore the hint, and the default differs between browsers. See MDN’s video reference for the attribute behavior.
Write down the intended outcome rather than treating the attribute itself as acceptance. For example: “Record whether the offscreen clip is requested on initial load, whether a request appears as it approaches the viewport, and what happens after a user presses play.” Compare those observations with the project’s expectation; none of these request timings is guaranteed by the preload hint.
Check the page states in order
Use the published page, a fresh browser session, and the actual video URL. In the Elements inspector, select the live <video> element and read its runtime preload, loading, and autoplay attributes. In the Network panel, filter for media requests or the video URL, then record the request time relative to page load, scrolling, and play. A network entry shows that a resource was requested; it does not prove that the whole file was downloaded. Avoid relying on a cached visit: a previous request can make a later state look as if it triggered loading.
- Initial load, video outside the viewport: For each run, record the browser and version, device, whether the cache was cleared (or that it was not), and the live
preload,loading, andautoplayvalues. Note whether a media request appears before scrolling or pressing play. Ifloading="lazy"is present, MDN says preload behavior is applied only when the video is near or within the viewport; do not expect the offscreen element to behave like an eager one. - Video approaching the viewport: In the same run, keep the environment and cache details recorded above; scroll until the video is near the visible area, then record whether a request begins and what resource is requested. With lazy loading, the browser uses a calculated distance from the viewport; “near” is not a fixed distance promised by the attribute.
- Visitor presses play: In the same run, retain the browser/version, device, cache status, and live attribute values with the record. Record whether a request starts or continues and whether playback begins. If
autoplayis present, interpret the earlier requests separately: MDN states that autoplay takes precedence over preload because playback needs the media to be downloaded. This guide concerns loading requests, not whether browser policy permits audible autoplay. - Repeat by target environment: Run the same sequence on the browsers and devices that matter to your audience. The MDN audio and video delivery guide notes that the
preloadattribute may be ignored by some mobile browsers, so a desktop result alone does not settle mobile behavior. The same guide also cautions thatautoplaymay be ignored by some mobile browsers.
Compare observations with the expectation
The table below is a hypothetical acceptance record, not a report of a test. “Request” means an observed video-resource entry in the Network panel, not proof that the whole file downloaded. Record the browser, device, and whether the session began with a clean cache alongside each run.
| Page state | Hypothetical setup | Hypothetical observation | Acceptance decision |
|---|---|---|---|
| Initial load; video offscreen | preload="metadata", loading="lazy", no autoplay; record browser/version, device, cache status, and live attributes | No video request before scrolling | Consistent with lazy loading; compare with the project expectation, not a preload guarantee |
| Video near viewport | Same recorded environment and attributes; scroll toward the element | A request appears after scrolling | Record whether and when it appeared; “near” depends on the browser’s calculated threshold |
| Visitor presses play | Same recorded environment and video; user activates controls | A request continues and playback begins | Confirms this observed user path in this environment only |
If your expected request does not appear, check the live element’s attributes first. A script or player may have changed the page from the markup you expected. Next, separate the lazy-loading and autoplay cases: temporarily compare the actual published configuration with a controlled test page that changes one attribute at a time. Treat this as diagnosis, not a universal fix. The documentation does not promise that changing preload will force a request.
Diagnose without overclaiming
A missing request while the video is offscreen and lazy-loaded is a reason to inspect the near-viewport state, not by itself evidence that the media URL is broken. Conversely, a request appearing does not establish that the whole file was downloaded: metadata is specifically an expectation about metadata, and browser media requests can be observed separately from playback readiness. For events such as loadedmetadata, canplay, and progress, use the distinction in MDN’s video element reference; do not treat any one event as proof of complete delivery.
If a request starts but the clip still does not play, this preload check has reached its limit. The supplied documentation identifies other possible delivery concerns, including unsupported formats, failed sources, and server MIME types. Investigate those separately from whether the request began. The MDN audio and video delivery guide describes format and delivery checks; it also notes that preload may be ignored by some mobile browsers.
Common questions
Does `preload="auto"` mean the complete file will be fetched?
No. It indicates that downloading the whole file may be appropriate, but the specification does not require the browser to follow the hint.
Does `loading="lazy"` disable preload?
Not exactly. MDN says lazy loading delays when preload behavior applies until the video is near or within the viewport. Test both the offscreen and near-viewport states.
If the request is present, is delivery verified?
Only partly. A request confirms that the browser requested a resource in that observed state. It does not, by itself, prove that the whole file downloaded or that playback will start without buffering. Record request timing separately from playback readiness.
Sources and next step
This guide interprets public documentation and uses explicitly hypothetical acceptance examples, not application tests. Controls and availability can change; verify the cited manual against your installed version.
For work created in Imagild, carry the input requirements and acceptance checklist into the film workspace. The external software controls discussed above belong to their respective products.