The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →URLbox bills screenshot API usage in monthly “renders,” not reliably one render per request. As of October 3, 2026, its published plans range from $19 per month for up to 2,000 renders to Enterprise plans starting at $3,000 per month. Request duration, output size, GPU acceleration, archive storage, and advanced features can increase render consumption, so estimate those before choosing a tier.
What a URLbox render is
URLbox uses “render” as its unit for generated output. The API reference gives screenshots, PDFs, and videos as examples. A plan’s monthly render allowance therefore describes output capacity, but it does not necessarily equal the number of API calls you can make.
As an Amazon Associate I earn from qualifying purchases.
URLbox’s pricing page says a request uses one render for each 30-second period it takes to render and one render for each 5 MB of file size. It also lists additional usage rules: GPU Acceleration uses twice the renders of a non-GPU request; Certified Archive adds one render per year of storage; and advanced features may consume additional renders. Check the current pricing terms for the exact treatment of a particular feature or request.
URLbox plans and published prices
The following vendor-published figures were observed on October 3, 2026. Prices exclude VAT at the prevailing rate and may change; verify the live URLbox pricing page before subscribing. The displayed per-1,000 figures for the first three plans are the page’s unit-cost figures, not a guarantee that every request has the same render cost.
#1 Best Overall
| Plan | Published monthly price and allowance | Requests per minute | Maximum timeout | File-size limit |
|---|---|---|---|---|
| Lo-Fi | $19/month for up to 2,000 renders; displayed $9.50 per 1,000 | 30 | 30 seconds | 2.5 MB |
| Hi-Fi | $49/month for up to 5,000 renders; displayed $9.80 per 1,000 | 60 | 90 seconds | 10 MB |
| Ultra | $99/month for up to 15,000 renders; displayed $6.60 per 1,000 | 250 | 300 seconds | No limit stated |
| Business | $495 base, then $3 per 1,000 renders; the pricing page also displays $498/month and lists at least 1,000 successful renders in its comparison table | 1,000 | 300 seconds | No limit stated |
| Enterprise | From $3,000/month, with custom capture limits and features | No limit stated | No limit stated | No limit stated |
Business’s page figures do not establish a general base allowance beyond the comparison table’s “at least 1,000 successful renders” wording. Do not assume that the $495 base includes a particular additional number of renders. The pricing page offers a seven-day trial for Lo-Fi, Hi-Fi, and Ultra, and a three-month trial on application for Business; check the live terms to confirm availability.
Do failed requests and cached screenshots use renders?
Failed requests
URLbox’s pricing FAQ says: “Unlike other APIs we don’t charge for requests that fail for any reason.” It defines a successful render as one that returns an image. This is the vendor’s stated policy; consult the current plan terms if a billing dispute or a specific failure case matters to your implementation.
Rank #2
![Free Fling File Transfer Software for Windows [PC Download]](https://m.media-amazon.com/images/I/41Vq6ZqHfjL._SL160_.jpg)
- Intuitive interface of a conventional FTP client
- Easy and Reliable FTP Site Maintenance.
- FTP Automation and Synchronization
Render Links and REST API caching are different
URLbox says Render Links cache screenshots for 30 days by default, with TTL and force options to change or bypass that behavior. Cached screenshots do not count against the monthly plan quota; first-time renders do. The API reference separately says synchronous REST API render requests are not cached or deduplicated. Do not apply the Render Link cache allowance to repeated REST API calls.
How to monitor monthly usage and overages
URLbox’s usage documentation describes these response headers for render quota tracking:
x-renders-used: renders used.x-renders-allowed: renders allowed.x-renders-remaining: renders remaining.x-renders-reset: when the usage count resets.
The same documentation distinguishes rate-limit headers from monthly render allowance. A per-minute request limit controls request frequency; it is not the monthly render budget.
The pricing FAQ says URLbox emails usage alerts at 80%, 90%, and 100%. It also says service is not cut off when quota is exceeded and describes automatic movement to the next tier with volume pricing. The published page does not establish one universal overage rate for every plan, so estimate costs from your plan’s live terms rather than applying a single flat rate.
How to choose a plan for screenshot API usage
Estimate monthly output after applying any render multipliers, then compare the tier limits with your workload’s operating constraints. A useful estimate is more than request count: include how long pages take, expected output sizes, and features that add renders.
- Monthly volume: project the number of screenshots, PDFs, and other outputs, then account for cache behavior where you use Render Links.
- Render complexity: allow for requests that cross 30-second duration periods or 5 MB file-size increments, GPU Acceleration, Certified Archive storage, and advanced features.
- Rate and timeout needs: compare your peak requests per minute and the longest render time you need against the plan limits in the table.
- Output-size needs: verify the file-size limit for the plan, especially if pages produce large images or PDFs.
- Storage destination: URLbox says Google Cloud Storage is the default. It supports saving to a customer’s own Amazon S3 bucket on Hi-Fi and above, and any S3-compatible storage provider on Ultra and above.
- Support and capture requirements: compare required features and support with the current plan details, particularly for Business or Enterprise needs.
For implementation details, use the URLbox quickstart and API reference. Plan prices and limits are vendor-published specifications, not independently audited comparisons, and can change.
Best Value
ScreenshotNeo as an alternative to try first
If you are comparing screenshot APIs, ScreenshotNeo is worth trying first: it removes cookie banners, newsletter popups, and chat widgets before capture, bills only clean shots, and its paid plans start at $5 for 3,000 shots.
Or skip the browser setup:
Make one GET request for a screenshot; see the ScreenshotNeo API docs for options.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpCookie banners, popups, and chat widgets are removed before the shot; bot checks, blank pages, and failed loads are never billed. An MCP server lets AI agents use the screenshot tools. The Free plan includes 1,000 screenshots per month with no card, and paid plans start at $5 for 3,000. Sign up for free.
Recommended Free Tools
Frequently Asked Questions
Does URLbox charge a render for every 30 seconds, or every started 30-second period?
The pricing page describes one render for each 30-second period a request takes, but the exact boundary treatment is not specified in the published material. Confirm the current billing interpretation with URLbox if your estimate depends on it.
Are URLbox’s listed prices inclusive of VAT?
No. URLbox says its listed prices exclude VAT at the prevailing rate.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
