Website Screenshot Generator
Pricing
from $7.00 / 1,000 capture extracteds
Go to Apify Store
Website Screenshot Generator
Capture bulk website screenshots and downloadable PDFs with full-page, element, mobile, dark-mode, and overlay-hiding controls.
Website Screenshot Generator
Pricing
from $7.00 / 1,000 capture extracteds
Capture bulk website screenshots and downloadable PDFs with full-page, element, mobile, dark-mode, and overlay-hiding controls.
1–1000 public HTTP or HTTPS page URLs. Add one URL per page, not a remote URL list. Embedded credentials and private destinations are not supported.
Capture the viewport or a full-page image. Full-page images are clipped at the configured height, 3840 CSS-pixel width or 8-million-physical-pixel cap and marked truncated. Ignored for PDF output.
Choose PNG, JPEG, or PDF output.
Browser viewport in CSS pixels. Density multiplies both image axes. Viewport-only images exceeding 8,000,000 physical pixels reject before browser work; reduce dimensions or density. Full-page images are clipped to the safety budget.
Automatic checks visible content and important images without waiting for background traffic. Full-page images and PDFs receive bounded lazy-loading scrolling; limits and unfinished lower content are reported in warnings. Selectors and extra delay still apply. Explicit DOM, load and network-idle settings retain existing behavior, including warned load fallback and narrowly verified product DOM fallback for image output. Lazy content may remain incomplete even when truncated=false; pending requests are never reported as idle.
Optional delay after the selected load milestone. Pages run one at a time. If these delays alone cannot fit runTimeSecs minus a five-second reserve, the run succeeds without captures and displays an explicit invalid-recipe warning before capture work. Split the URLs into smaller runs or reduce delayMs; navigation, rendering and storage need additional time.
Optional CSS selector. The first visible element's measured rectangle is captured for images. Elements exceeding 8,000,000 physical pixels fail without encoding or retrying; reduce element size or density. Ignored for PDF.
Optional CSS selector that must become visible before capture. Use this for client-rendered content.
Up to 100 CSS selectors to hide before capture, for example cookie banners or sticky overlays. Each selector can contain up to 2000 characters.
[]JPEG quality from 1 to 100. Used only when output format is JPEG.
Preferred browser color scheme for sites that support light or dark mode.
Maximum full-page image height in CSS pixels. Images also obey a 3840 CSS-pixel width and 8,000,000 physical-pixel safety cap, so actual height can be lower. Clipped images are marked truncated.
Maximum seconds for each navigation, selector wait or image operation, also subject to the total capture budget. A page can require several operations.
Retry transient navigation, proxy, and rendering failures. Validation and certificate failures are not retried.
Total capture budget from input processing, independent of the platform timeout. At expiry, the browser is closed and completed results are retained. Lower platform timeouts can still interrupt the run. Restarts and resurrection do not replay captures from an already started run.
Requested upper bound, retained for saved-task/API compatibility. The current safety ceiling is one active page, including navigation, image/PDF encoding and file persistence. Higher requested values do not create concurrent pages.
Managed datacenter proxy is the existing default for omitted API inputs and new forms. Existing managed groups/countries and customer proxy URLs remain supported. Explicit useApifyProxy:false without customer proxy URLs attempts direct access, with no paid fallback. Direct cloud egress may fail. Choose either managed proxy or customer URLs, not both. Proxy and browser usage can incur platform costs even when captures fail. No new Automatic strategy is available.