What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
HTML/CSS to Image (HCTI) counts images created, not HTTP requests, downloads, or the number of people who receive an image. A single API call can create several images in a batch, and some rendering settings can consume extra image credits. If deduplication is enabled and a request matches a recent image within the supported window, HCTI may reuse it instead of charging for a new render.
Does one screenshot API request count as one image?
Not necessarily. HCTI’s pricing FAQ says images count when they are created; downloading or distributing an already-created image does not multiply its usage. Its example is one image included in an email sent to 1,000 recipients: that is still one created image. The vendor’s stated rule is: “Images are counted when they are created; downloads and renders are unlimited.” (HCTI pricing)
The HTTP request is only the envelope for the work. A normal request that creates one image counts as one image, while a batch request that creates multiple variations should be estimated by the number of image records created. HCTI’s API supports batch creation; the current pricing page lists batches of up to 25 images on Basic and Pro, up to 100 on Scale, and no batch creation on Free. Check the live plan terms before relying on those caps. (HCTI API documentation; HCTI pricing)
What can make a request use more credits?
Long render delays
HCTI says a request may use additional image credits when it requires more rendering work, including when ms_delay is set above five seconds. The API documentation describes ms_delay as a wait before image generation, useful when JavaScript needs time to finish. Do not assume each delay setting maps to a fixed multiplier; the vendor does not establish one in the cited pricing guidance. (HCTI pricing; HCTI API documentation)
#1 Best Overall
Jumbo output
Jumbo images can also require extra credits. HCTI’s API docs say jumbo mode requires both jumbo_max_width and jumbo_max_height, supports dimensions up to 80,000 pixels, and consumes additional image credits. The pricing FAQ says the additional rendering depends on how many tiles are required, so do not apply a universal multiplier without checking the calculation for your request and plan. (HCTI API documentation; HCTI pricing)
When can deduplication avoid another image charge?
With deduplication enabled, HCTI can reuse a matching recent image rather than create another render. This is conditional: the request must match, deduplication must be on, and the match must fall inside the window available to the account. A retry or a visually similar request is not automatically free.
Rank #2
- Intuitive interface of a conventional FTP client
- Easy and Reliable FTP Site Maintenance.
- FTP Automation and Synchronization
The pricing page describes a standard one-month deduplication window for Free and Basic, custom deduplication up to six months for Pro, and extended deduplication up to one year for Scale. Applicable plans can control the window or disable deduplication. The API parameter dedupe_duration_s documentation cautions that defaults and permitted durations vary by image type and plan; check the current settings rather than assuming every account behaves the same. (HCTI pricing; HCTI deduplication parameter)
How to check actual image usage
Inspect response headers
HCTI documents three response headers for request-level usage:
Rank #3
x-renders-allowed: total image-credit allowance for the billing period.x-renders-consumed: image credits consumed by that request.x-renders-used: account usage so far in the current billing period.
These values help distinguish a one-image render from a batch or a request that consumed additional credits. (HCTI usage documentation)
Review the usage endpoint
The GET /v1/usage endpoint provides hourly, daily, monthly, and per-billing-period image-usage history. These are alternate views of the same usage, not separate totals to add together. The endpoint reports image history, not the number of Management API requests. (HCTI usage documentation)
Rank #4
What do HCTI plans and overages cost?
The figures below are vendor-listed prices and allowances checked on October 3, 2026. HCTI’s page does not show a publication date, and paid image volume is selectable, so the starting price alone does not establish the allowance for every volume option. Confirm the selected volume and current terms on the live pricing page before forecasting spend. (HCTI pricing)
| Plan or term | Vendor-listed figure (checked October 3, 2026) | Important qualification |
|---|---|---|
| Free | 50 images per month | No credit card required; batch creation is listed as unavailable. |
| Basic | Starts at $14 per month | Image volume is selectable; batch size listed up to 25 images. |
| Pro | Starts at $149 per month | Image volume is selectable; batch size listed up to 25 images. |
| Scale | Starts at $749 per month | Image volume is selectable; batch size listed up to 100 images. |
| Basic and Pro optional overages | $10 per 1,000 images | Optional, not enabled automatically. |
| Scale optional overages | $10 per 1,000 images or $50 per 10,000 images | Optional; confirm the selected overage option. |
Included image allowances reset at the start of each billing cycle and do not roll over, according to the pricing page. Because paid-tier volume is selectable, compare plans using the volume you would actually buy—not just the entry-level monthly price. (HCTI pricing)
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesBest Value
Is a 429 response an exhausted image allowance?
Not always. HCTI documents no per-second or per-minute request limit for image creation, but image credits and other plan limits still apply. Management API resource operations have separate read/write throttles, and either throttling or exhausted credits can produce HTTP 429. Waiting may help with a management rate limit; it does not restore exhausted image credits. Inspect the error message, the response headers, and current usage to identify which limit was reached. (HCTI FAQ; HCTI API documentation; HCTI usage documentation)
ScreenshotNeo: an alternative to try first
If you need a screenshot service where the charge is tied to a clean successful capture rather than every attempt, ScreenshotNeo is worth considering: it bills only clean shots, not bot checks or failed loads, and its lowest paid plan is $5.
One-call example
Make a GET request with the target URL and your API key. The response is the screenshot file; see the ScreenshotNeo API documentation for options.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp
ScreenshotNeo accepts cookie and consent banners like a visitor, then removes 60+ known consent platforms, newsletter popups, and chat widgets before capture; those steps can be turned off. Bot checks/CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, with response headers identifying the page verdict and billing status. Its MCP server gives AI agents tools for screenshots, page information, and PDF capture. The Free plan includes 1,000 shots per month with no card; paid plans start at $5 for 3,000 shots. Create a free ScreenshotNeo account.
Frequently Asked Questions
Does sending an existing HCTI image to more people use more credits?
No. HCTI counts the image when it is created; distributing or downloading that same image does not create another counted image.
Do hourly, daily, and monthly usage reports represent separate image totals?
No. They are alternate time-based views of image history, so adding them together would double-count usage.
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.




