The short answer
When to choose which
Choose ApiFlash when
- You need a large number of plain screenshots. Its Lite plan is $7 a month for 1,000 screenshots, its Medium plan $35 a month for 10,000 and its Large plan $180 a month for 100,000. [1] Its documentation gives a rate limit of 20 requests a second with a burst size of 400 requests. [3] PageVerified: One key can run up to 120 captures an hour, free or paid. Each key also has a daily share of the shared browser pool. A key capturing at that rate reaches it in under an hour.
- You need to capture pages behind a login. ApiFlash has headers and cookies parameters for capturing pages behind authentication. [2] PageVerified: Public
http and https pages only. It cannot log in, send cookies or set request headers. - You want free screenshots every month. Its Free plan gives 100 screenshots a month, with no credit card required. [1] PageVerified: A free key holds 25 credits, with no email and no card. The credits are given once.
- You need JPEG or WebP images, or ads and cookie banners removed. ApiFlash returns PNG, JPEG or WebP images. [2] Its Free, Lite, Medium and Large plan cards each list full page screenshots, mobile screenshots, blocking ads, hiding cookie banners and export to S3. [1] PageVerified: The request takes a URL, a format, a viewport, a full-page switch and a receipt switch. It has no settings for blocking ads, hiding cookie banners, custom headers, cookies or delays.
Choose PageVerified when
- You need the SHA-256 hash of the file and the UTC capture time in the same response as the capture, with a public receipt page by default.
- You want a PDF or the rendered HTML of the page as a file, as well as a PNG.
- You would rather buy a one-time pack of credits than start a plan that renews.
- Your agent has to buy its own access. It can pay over HTTP 402 with no person involved.
- Your agent speaks MCP and you want a hosted endpoint with nothing to install.
This page lists only what we could confirm on the other product's own pages. A feature that is not listed here may still exist, so check with its maker.
Facts checked 11 November 2026
Side by side
Scroll the table horizontally to see all fields.
PageVerified and ApiFlash compared| Topic | PageVerified | ApiFlash |
|---|
| Free use | A free key holds 25 credits, with no email and no card. The credits are given once. | Its Free plan gives 100 screenshots a month, with no credit card required. [1] |
|---|
| Paid price | One-time credit packs: $19 for 3,000 credits, $49 for 12,000 credits, $149 for 60,000 credits. A PNG or HTML capture costs 1 credit and a PDF costs 2 credits. | Its Lite plan is $7 a month for 1,000 screenshots, its Medium plan $35 a month for 10,000 and its Large plan $180 a month for 100,000. [1] |
|---|
| Request rate | One key can run up to 120 captures an hour, free or paid. Each key also has a daily share of the shared browser pool. A key capturing at that rate reaches it in under an hour. | Its documentation gives a rate limit of 20 requests a second with a burst size of 400 requests. [3] |
|---|
| Output | PNG, PDF or rendered HTML. One format per call. | ApiFlash returns PNG, JPEG or WebP images. [2] |
|---|
| Pages behind a login | Public http and https pages only. It cannot log in, send cookies or set request headers. | ApiFlash has headers and cookies parameters for capturing pages behind authentication. [2] |
|---|
| Request options | The request takes a URL, a format, a viewport, a full-page switch and a receipt switch. It has no settings for blocking ads, hiding cookie banners, custom headers, cookies or delays. | Its Free, Lite, Medium and Large plan cards each list full page screenshots, mobile screenshots, blocking ads, hiding cookie banners and export to S3. [1] Calls with the same parameters return a cached screenshot unless you ask for a fresh one. [2] |
|---|
| Waiting for the page | The renderer waits until the HTML is parsed, then up to 4 seconds for network activity to settle. There is no delay or wait-for-element setting. | By default ApiFlash waits until the network is idle before it captures, and it has delay and wait_for parameters. [2] |
|---|
The PageVerified column is read from the configuration this server runs. The numbers in square brackets point to the sources below.
One POST
A real PageVerified capture
A request like this one:
curl -s -X POST https://pageverified.com/api/v1/capture \
-H "authorization: Bearer $PAGEVERIFIED_API_KEY" \
-H "content-type: application/json" \
-d '{"url":"https://pageverified.com/pricing","format":"png","viewport":{"width":720,"height":400}}'
returns HTTP 201 with this body. The hash, time and receipt are from a real capture made by the production service. Only the download link is shortened.
{
"id": "6c5dbd00-8f1c-4b3a-9456-6d585e615e51",
"artifact_url": "https://... signed download link, valid for 24 hours ...",
"sha256": "748c89348b38d4e14e731d5071e409262a2f644c03461034d8c30e3353c5469c",
"captured_at": "2026-11-10T15:46:35.948Z",
"evidence_url": "https://pageverified.com/e/6c5dbd00-8f1c-4b3a-9456-6d585e615e51"
}
The receipt for that capture is public: /e/6c5dbd00-8f1c-4b3a-9456-6d585e615e51. It shows the same hash and time and lets anyone download the 42,580-byte PNG. How to check a file against its hash.
No key yet? This issues one with 25 credits. The key is shown once, so save it.
curl -s -X POST https://pageverified.com/api/v1/keys \
-H "content-type: application/json" \
-d '{"label":"my agent"}'
POST /api/v1/capture/record takes the same body and also returns a signed Capture Record, for the capture cost plus 4 credits. Anyone can check its signature against the public keys at /.well-known/pageverified-keys.json.
Read this part
What a PageVerified capture is, and is not
- The hash ties one file to one capture. If a file's SHA-256 equals the value on the receipt, it is byte for byte the file that receipt describes.
- The capture time is UTC from PageVerified's own server clock. For a signed Capture Record, outside time-stamp authorities later sign the record's hash with their own time, usually within 15 minutes; the record check at /verify shows it.
- A capture records what PageVerified's renderer saw at the recorded time. It is not a forensic chain of custody, proof of who wrote a page, or a legal certification.
- It captures public pages only. It cannot log in, send cookies or set request headers, and a site can show the renderer something different from what you see in your own browser.
- No uptime guarantee and no security or compliance certifications.
- Nothing on this page is legal advice.
From the live price list
PageVerified prices
- Free key. A free key holds 25 credits, with no email and no card. The credits are given once.
- Packs. One-time credit packs: $19 for 3,000 credits, $49 for 12,000 credits, $149 for 60,000 credits. A PNG or HTML capture costs 1 credit and a PDF costs 2 credits.
- Paying. Credit packs are one-time payments by card checkout, and a pack does not renew. Plans that renew each month are sold too. An agent can buy credits over HTTP 402 with no person involved.
- Limit. One key can run up to 120 captures an hour, free or paid. Each key also has a daily share of the shared browser pool. A key capturing at that rate reaches it in under an hour.
These numbers are read from the price list this server runs. The full list, with the cost of every tool, is on the pricing page.
Last checked 11 November 2026
Sources and dates
- ApiFlash home page, with its plans. Checked on 11 November 2026 from https://apiflash.com/
- ApiFlash questions page. Checked on 11 November 2026 from https://apiflash.com/faq
- ApiFlash documentation. Checked on 11 November 2026 from https://apiflash.com/documentation
Prices and features change. If something here is out of date, tell us and we will check it again. After 120 days without a fresh check this page takes the comparison down by itself.
PageVerified has no connection with ApiFlash. The name is used only to say which product is being compared. This page has no affiliate links, and PageVerified is paid nothing if you choose the other product.
Next steps
Other comparisons: ScreenshotOne alternative · Urlbox alternative · Page Vault alternative for developers · Wayback Machine alternative.