GrabzIt Pricing for Website Screenshots: Plans and Usage Limits
Compare GrabzIt’s screenshot plans, published request limits, cache durations and trial terms. Check its live pricing selector for current prices and quotas.
Short answer: GrabzIt lists five paid screenshot packages: Micro, Entry, Professional, Business and Enterprise. Its published request ceilings range from 75 to 180 requests per minute, and maximum cache durations range from 90 minutes to 12 hours. The exact current prices and included capture quotas are controlled by a live pricing selector and were not exposed in the available official page rendering, so check the selector for your currency, billing choice and geography before budgeting.
GrabzIt offers automatically renewing monthly or yearly subscriptions and one-time monthly or yearly purchases. Its screenshot API page advertises a seven-day trial without a credit card; trial API captures carry a GrabzIt watermark. These details and the plan limits below come from GrabzIt’s published material, rather than independent performance measurements. GrabzIt pricing, Screenshot API, premium features
GrabzIt plans at a glance
| Plan | Published request ceiling | Maximum cache duration | Other published distinctions |
|---|---|---|---|
| Micro | 75 requests/minute | 90 minutes | Standard support |
| Entry | 90 requests/minute | 3 hours | Standard support |
| Professional | 120 requests/minute | 6 hours | Priority support, custom HTTP proxies and encrypted captures |
| Business | 150 requests/minute | 12 hours | Priority support, custom HTTP proxies and encrypted captures |
| Enterprise | 180 requests/minute | 12 hours | Higher-tier features and a stated 99.99% uptime SLA |
GrabzIt publishes these request and cache specifications on its premium-features page. They are plan specifications, not a promise that every individual capture will complete within a particular time. Check current terms and SLA scope directly with GrabzIt before relying on them.
How to find the current price and capture allowance
- Open the official pricing selector.
- Select the billing mode you are considering: monthly or yearly subscription, or a one-time monthly or yearly purchase.
- Confirm the displayed currency and any location or payment settings that affect the quote.
- Record the included captures and their reset period, then compare that allowance with your expected monthly or annual volume.
- Check renewal or expiry terms, trial watermark treatment, support, and any premium features your workload needs.
The available official page rendering did not expose selected prices or capture counts. Do not use an old cached price, an unverified currency conversion or a third-party pricing aggregator as a current quote. The selector is the source to consult immediately before purchase.
Understand the limits before choosing a tier
Capture allowance and request rate are different
The package’s monthly or yearly capture quota is the total allowance over its billing period. The requests-per-minute figure is a throughput ceiling. A plan can have enough total captures for a workload and still throttle a burst that exceeds its per-minute rate. Since the current capture quotas were not visible in the research rendering, retrieve them from the live selector before calculating capacity.
Cache duration can reduce repeat capture usage
GrabzIt documents plan-specific maximum cache durations. Its JavaScript API documentation says an identical request can return a cached screenshot without using another capture allowance; a cache option can disable that behavior. Confirm how the cache parameter behaves for the API you use and the freshness your application requires. JavaScript API documentation
Monitor checks are not screenshot captures
GrabzIt treats monitor checks as a separate allowance for checking pages for changes. Screenshot or scrape tasks do not consume those checks unless the monitor page functionality triggers the task. When monitor checks run out, additional pages cannot be monitored until the allowance resets or another package is purchased. Monitor checks documentation
Other feature constraints
GrabzIt’s premium feature documentation lists full-length captures, target HTML element captures and full-scale captures. It documents a maximum image width of 10,000 pixels with unbounded height. Verify the current feature matrix for the exact tier availability and consider the practical memory and file-size implications of very tall captures.
Estimate the plan your workload needs
- Estimate total volume. Count unique pages and recaptures per billing period. Treat cache hits separately and do not assume every repeated request is charged unless the API’s cache conditions are met.
- Estimate peak traffic. Divide the largest burst into a one-minute window and compare it with the tier’s published requests-per-minute ceiling. Schedule or queue jobs if your burst exceeds it.
- Decide freshness. Longer cache windows may reduce repeat work, but cached captures can be stale for frequently changing pages. Disable or shorten caching where fresh output matters.
- Account for required features. Check whether you need full-page or element captures, proxies, encryption, priority support or an Enterprise SLA.
- Compare purchase terms. For a short project, compare one-time purchase options with a renewing subscription. For ongoing use, compare monthly and yearly subscription totals and confirm renewal terms.
Because price and included capture counts depend on the selector’s current choices, a trustworthy cost-per-capture calculation requires the live price, allowance and billing period. Divide the quoted total by the included captures only after confirming whether the amount is recurring, prepaid or subject to expiration.
Trial and free access
GrabzIt’s screenshot API page advertises a seven-day free trial with no card required and says trial API screenshots include a watermark. This is a time-limited trial, not evidence of a continuing free monthly screenshot quota. The official pricing selector and account terms should be checked for current trial eligibility and what happens when the trial ends.
An older support-community response from 2021 described a 500-capture monthly limit for a free Screenshot Tool, but it also said those limitations were not finalized. It does not establish a current 2026 allowance and should not be used for planning.
API details that affect implementation and usage
- Authorized domains: GrabzIt’s JavaScript API documentation says browser-side applications must authorize their domains for the application key.
- Keep credentials server-side: GrabzIt warns against exposing an application key in client-side code. Route requests through a backend when a key must remain secret.
- API feature differences: Its REST API documentation says some functions, including merging and encryption, are unavailable through that REST API. Confirm the API surface supports the feature before building around it.
- Cache behavior: Matching parameters may reuse a cached screenshot under the documented conditions. Disable caching where repeat requests must reflect current page content.
Sources: REST API documentation and JavaScript API documentation.
Common pricing and usage mistakes
| Problem | Why it happens | What to do |
|---|---|---|
| Budget uses an old price | Prices vary with currency and purchase or subscription choice, and selector values can change. | Use the live selector and note currency, billing mode, region and date when budgeting. |
| Monthly allowance appears exhausted early | Repeated uncached captures may count separately; the plan’s quota and cache conditions matter. | Review request parameters and caching behavior, then compare usage with the plan’s actual capture allowance. |
| A burst is throttled despite remaining quota | Total-period allowance does not override the requests-per-minute ceiling. | Queue or pace requests, or select a tier whose published rate ceiling matches peak demand. |
| Trial output has a watermark | GrabzIt states that trial API captures include one. | Check paid-plan terms if production output must be watermark-free. |
| Browser-side API calls expose a key | Client code is visible to users. | Keep secret credentials on a server, or use the documented domain authorization where appropriate. |
| A required REST feature is unavailable | GrabzIt documents that some functions, including merging and encryption, are not available through its REST API. | Check the API-specific documentation and select a supported integration path before implementation. |
Or skip the browser setup
If your goal is to capture pages without managing a browser pipeline, ScreenshotNeo is the alternative to try first: clean shots are billed only when they are clean. One GET request returns an image or PDF. See the ScreenshotNeo API documentation.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpimport requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);Cookie banners are accepted or removed before the shot, along with known newsletter popups and chat widgets; each cleanup step can be turned off. Bot checks, blank pages and failed loads are never billed, and response headers say the page verdict and whether it was billed. An MCP server gives AI agents tools to take screenshots, inspect page information and capture PDFs. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000. Sign up free for ScreenshotNeo.
FAQ
Does GrabzIt have a permanent free screenshot API plan?
The official API page advertises a seven-day trial. The reviewed material does not substantiate an ongoing free monthly API allowance.
Are monitor checks the same as screenshot captures?
No. GrabzIt defines monitor checks as a separate allowance for checking pages for changes.
Which GrabzIt tier has the highest published request rate?
Enterprise, at 180 requests per minute in GrabzIt’s published premium feature specifications. Verify the current terms before relying on that ceiling.
Can I quote an exact current price from this guide?
No. The exact selected price and capture quota were not visible in the official page rendering used for this guide. Use GrabzIt’s live pricing selector for a current quote.
