Screenshot Pro: Website Screenshot and PDF
Pricing
from $4.50 / 1,000 screenshots
Screenshot Pro: Website Screenshot and PDF
Full-page website screenshots that actually load lazy images. PNG, JPEG or PDF for desktop, tablet and mobile in one run, with cookie banners removed.
Pricing
from $4.50 / 1,000 screenshots
Rating
0.0
(0)
Developer
Jefri Maruli
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
18 days ago
Last modified
Categories
Share
What does Screenshot Pro do?
Screenshot Pro captures screenshots of any public website. Give it a list of URLs and get back full-page or element screenshots as PNG, JPEG or PDF, for desktop, tablet and mobile in a single run.
Use it for:
- Visual monitoring and archiving of competitor pages, landing pages and pricing pages
- Thumbnails and previews for directories, link previews and dashboards
- QA checks of responsive layouts across devices
- Compliance and evidence captures (ads, claims, published content)
- Feeding page images to AI and vision models
Why Screenshot Pro?
- Lazy-loaded images actually load. The page is scrolled from top to bottom and every image is awaited before capture, so full-page shots don't come back with grey boxes.
- Cookie banners and chat bubbles hidden (OneTrust, Cookiebot, Didomi, Usercentrics, Intercom, HubSpot, Tawk and more).
- Desktop, tablet and mobile in one run. One screenshot per URL per device.
- PNG, JPEG or PDF. PDF keeps backgrounds and uses the screen layout, not the print layout.
- Element screenshots via a CSS selector, dark mode, wait for selector and extra delay for pages that load late.
- Batch friendly. Hundreds of URLs, captured in parallel. A broken URL is reported in the results and doesn't stop the run.
How much does it cost?
$6 per 1,000 screenshots, with no memory or compute fees on top. The only other charge is a start fee of $0.00005 per GB of memory, which is $0.0002 per run at the default 4 GB. Failed pages are free. Set a maximum cost per run and the Actor stops when it is reached.
Input
| Field | Description | Default |
|---|---|---|
urls | Pages to capture. example.com is treated as https://example.com. | required |
devices | Any of desktop (1920x1080), tablet (820x1180), mobile (390x844) | ["desktop"] |
format | png, jpeg or pdf | png |
fullPage | Whole scrollable page instead of the visible viewport | true |
selector | Capture only the first element matching this CSS selector | |
hideCookieBanners | Hide consent popups and chat widgets | true |
darkMode | Request the site's dark color scheme | false |
waitForSelector | Wait for this element before capturing | |
delayMs | Extra wait after load, max 30000 | 0 |
jpegQuality | 1 to 100 | 80 |
timeoutSecs | Per-page timeout | 60 |
maxConcurrency | Pages captured in parallel, 1 to 10 | 3 |
Example:
{"urls": ["https://apify.com", "example.com"],"devices": ["desktop", "mobile"],"format": "jpeg"}
Output
Each screenshot is saved in the run's key-value store, and one row per screenshot goes to the dataset:
{"url": "https://apify.com/","finalUrl": "https://apify.com/","title": "Apify: Full-stack web scraping and data extraction platform","device": "mobile","format": "jpeg","key": "apify.com_mobile_3f2a9c1b7d4e.jpg","screenshotUrl": "https://api.apify.com/v2/key-value-stores/<storeId>/records/apify.com_mobile_3f2a9c1b7d4e.jpg","sizeBytes": 412345,"capturedAt": "2026-10-03T12:00:00.000Z"}
Failed pages produce a row with an error field instead.
Limits
- Only public
httpandhttpspages. Pages behind a login are not supported. - Infinite-scroll feeds are scrolled for a limited distance, then captured.
- Some sites block automated browsers. Those pages come back with an
error, and you are not charged.
FAQ
Why do other screenshot tools return grey boxes instead of images?
Many sites only load images when you scroll to them. Screenshot Pro scrolls the whole page and waits for every image before capturing, so full-page shots come back complete.
Can I capture a page behind a login?
No. Screenshot Pro only captures public pages.
Can I capture just one part of the page?
Yes. Put a CSS selector such as #pricing or .hero in "Element selector" and only that element is captured.
How do I take screenshots on a schedule?
Create a Schedule in Apify Console (for example daily at 09:00) and point it at a saved task with your URLs. Each run stores new screenshots, which works for visual monitoring and archiving.
How do I use it from code?
Call it through the Apify API or the apify-client package for JavaScript or Python, then download each file from screenshotUrl in the dataset.
import { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: process.env.APIFY_TOKEN });const run = await client.actor('jefrimaruli/screenshot-pro').call({urls: ['https://example.com'],devices: ['desktop', 'mobile'],format: 'png',});const { items } = await client.dataset(run.defaultDatasetId).listItems();console.log(items.map((i) => i.screenshotUrl));
What happens if a page fails?
The dataset gets a row with an error field for that page, the rest of the run continues, and you are not charged for it.