ShrinkTheWeb vs Microlink for Website Previews

Short answer: Microlink is the easier option to evaluate from current public documentation: it describes one hosted API for metadata, screenshots, PDFs, Markdown, HTML, and other rendered outputs. ShrinkTheWeb has older documentation for a screenshot thumbnail service, but its current service status, options, limits, and prices could not be confirmed from current official sources. The Drupal module’s unsupported notice applies to that integration module, not necessarily to the ShrinkTheWeb service itself.

If your requirement is simply a screenshot API, ScreenshotNeo is the first alternative to try: it removes known consent banners, newsletter popups, and chat widgets before capture, and bills only clean shots. The comparison below keeps vendor claims attributed and avoids treating the older ShrinkTheWeb integration documentation as a description of the current service.

1. What each service is documented to do

Microlink documents a hosted API that returns normalized metadata by default and can also return screenshots, PDFs, Markdown, HTML, iframe embeds, or browser-function results. Its screenshot documentation describes viewport and full-page captures, device emulation, and capture options. These are descriptions published by Microlink, not independent performance findings. Microlink API · Screenshot parameter documentation

ShrinkTheWeb is described by older Drupal documentation as a service that generates and caches website thumbnails. That 2019 guide documents account keys and options such as custom size and specific-page captures, with some options depending on account upgrades. It cannot establish which features, plans, or limits are available today. Drupal setup guide

The Drupal.org project page marks the ShrinkTheWeb Drupal module unsupported as of January 31, 2022. This is a warning about the integration module; it does not establish that the vendor service has shut down. Drupal module project page

2. At-a-glance comparison

Option	What the available evidence supports	Best fit	Important caveat
1. ScreenshotNeo	Website screenshot API and MCP server; PNG, JPEG, WebP, or PDF output. Cookie/consent banners, newsletter popups, and chat widgets can be removed before capture. Failed or unclean captures and cache hits are not billed.	Developers who want website captures with cleanup, explicit page verdict and billing headers, or MCP tools for AI agents.	These are ScreenshotNeo product facts. Check its docs for request parameters and integration details.
2. Microlink	Current product documentation describes metadata and multiple rendered outputs from one API. Its API page lists a free tier of 25 requests per day and Pro at $49/month for 46,000 requests/month.	Teams that may need metadata, screenshots, PDFs, or text-like rendered outputs from one service.	Plan figures and behavior are vendor-published and can change; verify on the official page before budgeting.
3. ShrinkTheWeb	Older integration material documents website screenshot thumbnails, account keys, caching, and historical capture options.	Teams maintaining an existing integration that can confirm the service still meets their needs.	Current official service status, pricing, quotas, feature set, and support could not be verified in the research for this article. Do not rely on old module docs as current plan documentation.

This is a practical ordering by what a developer can verify and evaluate today, not a head-to-head performance ranking. No independent benchmark was verified for these services, and the available evidence does not support declaring Microlink or ShrinkTheWeb a universal winner.

3. Choosing for your preview use case

Choose based on the output you actually need

Link cards: If you need title, description, and image metadata, Microlink documents metadata as its default response. ShrinkTheWeb’s older material centers on screenshot thumbnails, so check whether it provides the structured metadata your application needs before choosing it.
Visual thumbnails: A screenshot API should be evaluated for page selection, viewport size, full-page behavior, image format, and how it handles consent banners and dynamic content. Microlink documents screenshot controls; the older ShrinkTheWeb guide lists historical sizing and specific-page options, but current parity is unverified.
Several output types: Microlink documents screenshots and additional output types through the same API. ScreenshotNeo focuses on screenshots and PDFs and also provides MCP tools for agents.

Check freshness and caching

Microlink’s current API page describes 24-hour default response caching and stale responses served while a fresh response is fetched. It also describes configurable TTL on Pro. These are vendor-described behaviors; verify the current documentation and decide whether a cached preview is acceptable for your use case. The older ShrinkTheWeb Drupal guide exposes a local thumbnail retention setting, but that is not evidence of the current service’s cache policy. ScreenshotNeo offers caching with a TTL you choose.

Compare prices using verified terms

Microlink’s API page lists 25 requests per day on Free and $49 per month for 46,000 requests per month on Pro. Treat these as observed vendor terms, not a guarantee: plan details can change. Current official ShrinkTheWeb pricing could not be confirmed, so the third-party snapshot of $4.95 per month should not be treated as a current quote or used in a price-equivalent comparison.

ScreenshotNeo lists 1,000 shots/month free with no card; paid plans are Starter $5 for 3,000, Growth $15 for 15,000, Pro $39 for 60,000, Scale $99 for 250,000, and Business $249 for 1,000,000. Yearly billing gives two months free, and every feature is on every plan. See ScreenshotNeo for the product and the API documentation.

4. Try Microlink with a simple request

Microlink’s documented free endpoint accepts a URL as a GET parameter. The following examples request a screenshot of a public page. The response is JSON containing screenshot information; read the returned image URL or use the documented embed option if your integration needs image bytes directly. Microlink documents the free allowance as 25 requests per day without a key. Official API details

cURL

curl -G 'https://api.microlink.io' \
  --data-urlencode 'url=https://example.com' \
  --data-urlencode 'screenshot=true'

Python

import requests

response = requests.get(
    "https://api.microlink.io",
    params={"url": "https://example.com", "screenshot": "true"},
    timeout=90,
)
response.raise_for_status()
payload = response.json()
if payload.get("status") != "success":
    raise RuntimeError(payload)
print(payload["data"]["screenshot"]["url"])

Node.js

const params = new URLSearchParams({
  url: 'https://example.com',
  screenshot: 'true'
});

const response = await fetch(`https://api.microlink.io?${params}`);
if (!response.ok) throw new Error(`HTTP ${response.status}`);
const payload = await response.json();
if (payload.status !== 'success') throw new Error(JSON.stringify(payload));
console.log(payload.data.screenshot.url);

For Microlink Pro, its API page says to send the token in the x-api-key header to pro.microlink.io. Keep secrets on your server rather than exposing them in browser code. Consult the current screenshot parameter reference for option names and response details.

5. Questions to settle before adopting either service

Does it return the right artifact? Test a metadata card and a visual thumbnail separately if you need both. Confirm whether your app consumes JSON, a hosted image URL, or raw image bytes.
Does it capture the right part of the page? Try the homepage and an interior route. Check full-page versus viewport output, responsive layout, and pages that render after JavaScript.
Does it produce a clean preview? Test consent overlays, newsletter dialogs, chat widgets, and ads. A capture that includes an overlay may technically succeed but still be unusable.
Can you verify service status and terms? For ShrinkTheWeb, confirm service availability, account creation, API access, support, request allowance, pricing, and current options directly with the provider before building a dependency.
What happens under load or on errors? Check rate-limit behavior, cache controls, retry guidance, timeouts, and whether an error is distinguishable from a valid screenshot result.
Can the credentials stay private? Use a server-side integration for secret keys. If a service supports public image URLs or signed links, review its docs and access model before embedding them in a public page.

6. Reliability, performance, and cost considerations

Reliability

A website capture depends on both the screenshot service and the target site. A target may be slow, require login, block automated browsers, or render content asynchronously. Validate the response status and payload before storing or showing an image. Build a fallback state for a missing preview rather than making page rendering depend on a third-party capture completing synchronously.

Microlink describes rate-limit headers and cache behavior on its API page. Its page states that parallel requests are allowed within quota and that the free tier returns a rate-limit error when the allowance is exceeded. Treat this as vendor documentation and implement handling based on the current API reference. For ShrinkTheWeb, current quota and retry behavior were not verified.

Performance

Capture when a link is first seen or in a background job, then serve the stored preview from your own cache or CDN.
Choose viewport capture for compact cards; full-page captures can create much taller assets and larger files.
For dynamic pages, wait for a meaningful element or application state rather than assuming the initial document load means the content is ready. Microlink documents selector and navigation waits in its browser automation options.
Use a refresh policy appropriate to the page. Longer caching reduces repeated work but makes changed pages take longer to appear in previews.

Cost

Estimate monthly demand from unique URLs, refresh frequency, retries, and whether cached requests count against a plan. Do not compare a monthly price without comparing the included request window and what counts as a request. Microlink’s documented cache hits are free according to its API page. ScreenshotNeo states that cache hits and unsuccessful or unclean captures are not billed, and its responses identify page verdict and billing status with X-Page-Verdict and X-Billed headers. Current ShrinkTheWeb billing terms remain unverified.

7. Or skip the browser setup

ScreenshotNeo provides a one-call screenshot API. This example uses the supplied API pattern; replace the placeholder with your key and change the target URL as needed. See the ScreenshotNeo docs for options and response handling.

curl -G "https://api.screenshotneo.com/v1/shot" \
  -d access_key=YOUR_API_KEY \
  --data-urlencode url=https://stripe.com \
  -o shot.webp

import 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, popups, and chat widgets are removed before the shot; each cleanup step can be turned off.
Bot checks, blank pages, failed loads, timeouts, and cache hits are never billed. Responses include page-verdict and billing headers.
An MCP server lets AI agents, including Claude, Cursor, and other MCP clients, use take_screenshot, get_page_info, and capture_pdf.
1,000 screenshots a month are free with no card; paid plans start at $5 for 3,000.

8. Troubleshooting

Symptom	Likely cause	What to do
Microlink returns an error instead of screenshot data	The request failed, the target did not render as expected, or the API rejected the request.	Check HTTP status and the JSON status/error fields; confirm the target URL is publicly reachable and the query parameters are encoded. Consult the current API reference for the error code.
Screenshot shows a spinner or empty app shell	The page content appears after initial navigation.	Use a selector or suitable wait option supported by the service. Prefer waiting for the chart, card, or heading your preview needs over an arbitrary long delay.
Preview contains a cookie dialog or newsletter overlay	The capture service did not remove that site-specific overlay, or the page uses a custom consent implementation.	Check the provider’s cleanup controls. With ScreenshotNeo, known consent platforms, newsletter popups, and chat widgets are removed before capture; individual cleanup steps can be disabled.
Microlink request is rate limited	The documented plan allowance has been exceeded.	Inspect the rate-limit headers, reduce duplicate captures, cache results in your application, and review current plan limits.
ShrinkTheWeb integration instructions do not match your Drupal setup	The available setup guide is dated 2019 and the Drupal module is marked unsupported.	Do not assume current compatibility from that guide. Confirm the service and maintained integration path with the provider, or use a currently documented API.
A preview is stale	Your app or capture provider is serving a cached result.	Review the provider’s current TTL and refresh behavior, then align it with how often the source page changes. Microlink documents a 24-hour default and configurable Pro TTL; ScreenshotNeo lets you choose a cache TTL.
Your app leaks an API key	The request is being made from public frontend code or the key is included in a public URL.	Move authenticated requests to a backend endpoint and store the key in server-side configuration. Never commit secrets to source control.

9. FAQ

Is ShrinkTheWeb shut down?

The available evidence does not establish that. Drupal.org marks its ShrinkTheWeb module unsupported; that notice is about the module. The service’s current status could not be verified here.

Is Microlink only for screenshots?

No. Its current API documentation describes metadata by default and additional outputs including screenshots, PDFs, Markdown, and HTML.

Which service is cheaper?

There is not enough verified current pricing to compare ShrinkTheWeb fairly. Microlink lists Free at 25 requests per day and Pro at $49/month for 46,000 requests/month; confirm those terms on its official page. ScreenshotNeo’s published plans are listed above.

Can I use a screenshot API for link previews?

Yes, if the preview design needs a visual image. If it needs a page title, description, and Open Graph metadata, verify that the API returns those fields too or combine screenshot and metadata steps.

What should I test before switching providers?

Run representative public, dynamic, long, and overlay-heavy URLs; compare output dimensions and freshness; then verify current limits, costs, error handling, and credential requirements.