AutoCod.
Get AutoCod

Help & guides

Make your next capture a good one.

Start with a short capture. These steps help you spot page and browser limits before a longer session.

Before you capture

  1. Use desktop Chrome and a regular HTTP or HTTPS page. Settings, extension pages, new tabs, and the Chrome Web Store cannot be captured.
  2. Sign in inside AutoCod and verify your email. Website and extension sessions are separate.
  3. Close private notifications and hide any personal information you do not want in the result.
  4. Let fonts and images load. Expand the sections you need and dismiss cookie notices.
  5. Choose recording or screenshot. Screenshot controls open in a persistent workspace so closing the popup does not discard your settings. Set your scroll pace and keep the source tab open until capture finishes.
  6. For recordings, leave Output format on Auto to use native MP4 when your browser supports it, with WebM as the fallback. Choose WebM explicitly when you need that format. Use Native · 1× output to preserve source detail with the least processing; upscaling does not add detail to the captured page.

Troubleshooting

Capture will not start

Open an ordinary website and click the AutoCod icon again to grant access to that tab. Finish or stop an existing capture. On managed computers, ask your administrator whether tab capture and extensions are permitted.

A screenshot misses content or repeats a header

Wait for the page to settle. For nested scrolling panels, infinite feeds, sticky headers, or pages that keep adding content, capture a shorter section or try a recording. Very long screenshots can be split into bounded parts to stay within browser canvas and memory limits; inspect every part before sharing. Infinite pages are bounded rather than captured indefinitely.

The result is blank or contains a blank video

Protected media, cross-origin embeds, and some GPU-rendered content cannot always be captured. Try a regular text-and-image page to distinguish page restrictions from an extension problem.

A recording stutters or stops

Keep the source tab open, use Native · 1× output, reduce presentation effects, and close resource-heavy tabs. AutoCod targets up to 60 FPS, but the result depends on the frames your source tab renders, page complexity, hardware, browser scheduling, and available memory.

MP4 is unavailable

Auto prefers native MP4 when your browser supports recording it and falls back to WebM otherwise. You can also select WebM explicitly in Output format. The saved file uses the format shown in the recording preview; no separate MP4 conversion download is required.

Sign-in or verification fails

Check your connection and spam folder, then use the extension’s resend verification control if needed. Wait before retrying repeated attempts. A site service outage should not stop public help pages from loading.

Report a reproducible problem

Include your Chrome and AutoCod versions, capture mode, settings, page address if public, and the exact steps and error message. Remove personal information from attachments. Never send passwords or authentication tokens.

Contact support →