Website Scroll Video: Capture and Animate a Page

Create a silent scroll animation from a remotely captured page

Website Scroll Video Generator first obtains a full-page screenshot of a permitted public URL, then animates that still image on a local canvas and records the canvas stream. The result is a silent video of an image moving through a viewport. It is not a live recording of interactions, loading states, page audio or an actual user browsing session.

Use it for a visual walkthrough of a page you control, a layout comparison or an authorized presentation. The existing URL field, speed presets, aspect-ratio selector, mockup-frame options and preview remain the workspace. A remote renderer can see a different page state from your browser, so inspect the captured content before presenting the result as a faithful account of what every visitor sees.

Choose the settings before generating

Enter a public-domain HTTP or HTTPS address without credentials, IP literals or a nonstandard port. An omitted scheme receives HTTPS. Select the speed and output aspect ratio, then choose a browser-window mockup or a borderless canvas and a background. While generation runs, settings stay fixed so the file corresponds to the configuration that started the job.

Desktop output uses 1280 by 720 pixels, mobile output uses 720 by 1280 and square output uses 800 by 800. The screenshot request uses a width of 390 for mobile capture and 1280 otherwise. Capture width and output dimensions are separate: a square video does not imply the target website was rendered in an 800-pixel-wide browser.

Choose Generate Video and keep the tab visible through capture and recording. Capture can take tens of seconds before recording starts. The speed control describes motion across the output canvas, not an assumed source-page frame rate. A browser mockup reduces the visible image area. The duration calculation accounts for that viewport rather than treating the decorative header as page content.

Original short-page exercise

Publish a small page you own with three clearly labeled colored sections and enough height to scroll. Choose desktop, borderless canvas, pure-white background and a speed of 120 pixels per second. The expected output is a silent recording that starts at the top section and moves toward the bottom of the captured image. It should not invent motion inside those sections or play embedded audio.

In a controlled screenshot fixture, an image 1280 pixels wide and 1920 pixels tall with desktop borderless output leaves 1200 image pixels to scroll after subtracting the 720-pixel viewport. At 120 pixels per second, the predicted duration is ten seconds. A short image with no scrollable distance still records for at least two seconds. These calculations describe the fixture, not a measured duration for every remote site.

Repeat the exercise with a browser mockup. The visible viewport is smaller and the decorative header stays fixed while the screenshot moves inside it. Then try mobile output and confirm its actual 720-by-1280 dimensions in a player or file inspector. Record provider capture and local recording separately: a simulated screenshot verifies canvas behavior but cannot establish that the live provider currently captures your URL.

Supported recording containers and limits

The browser selects a supported MediaRecorder format, preferring available WebM options and using MP4 where supported. The final label and downloaded extension follow the recorder’s actual container. Choosing a .mp4 filename cannot convert WebM bytes into MP4. Use a compatible local editor if a destination requires a codec or container that your browser does not record.

Recording requests a canvas stream at thirty frames per second, but hardware, browser scheduling and background-tab throttling affect delivery. The tool does not promise a constant measured frame rate or professional encoding quality. A recording must contain nonempty chunks; recorder failures and deadline expiry produce an error instead of a successful empty video.

The image response budget is twenty MiB, with dimensions up to 8192 pixels per side and sixteen million pixels total. The derived recording duration must not exceed two minutes. For a longer screenshot, increase speed or use a shorter page; the tool rejects an excessive job rather than silently claiming complete coverage. An exceptionally long remote page may exceed the image budget before recording can begin.

Capture providers and processing details

The first capture request goes to the SimplyUtils full-page-screenshot endpoint with your URL and capture width. If that service is unavailable, the interface tries pageshot.site as a fallback. That fallback also receives the target URL and capture settings. The target website can observe a remote visit. Avoid tokens, private dashboards, signed links and material that should not be sent to a renderer.

The primary request expires after forty-five seconds, and the fallback request has a fifty-second deadline. A readable accepted image is required before local recording. Image decoding has its own bounded wait. Provider filters, quota, network controls, login requirements and bot challenges can prevent capture even when the same address opens in your personal browser.

After capture, canvas animation and video recording happen locally. Object URLs and media tracks are released when work finishes, fails or the page closes. The page does not submit the completed canvas video to a server for encoding. That local synthesis step is separate from the remote capture and any site-wide analytics or infrastructure logs described in the Privacy Policy.

Troubleshooting and appropriate use

If no video appears, identify whether capture, decoding or recording failed. Test a small public page you own and confirm the browser supports canvas captureStream and MediaRecorder. If capture succeeded but recording times out, keep the tab visible, shorten the job and close memory-heavy tabs. A paused background tab can delay animation without providing evidence that the source website itself is broken.

If the video is incomplete, compare it with the captured image. Consent overlays, lazy-loaded sections, fixed-position elements and location-specific responses can alter the screenshot. The animation cannot reveal content absent from that image. A capture-service wait does not guarantee that every target script or scroll-triggered component ran. Do not treat this output as Google’s rendering test or as evidence that a search crawler indexed all sections.

Save the file only after preview is available and check playback in the intended destination. Use pages you are entitled to capture and share. Report the public test URL, selected settings, browser, output container and exact error, excluding credentials. The tool does not guarantee platform compatibility, copyright clearance, flawless frame pacing or the availability of either remote capture provider.