Install Microlink’s official microlink.io package, call microlink.screenshot(url, options), and use the returned screenshot asset URL. The SDK handles the request for you; it does not automatically save an image file to your computer.
Take your first screenshot with the Microlink Node.js SDK
Install the package in your project:
npm install microlink.io
The documented example uses ES modules and top-level await. Save it as index.js in a project configured for ES modules, such as one whose package.json contains "type": "module":
As an Amazon Associate I earn from qualifying purchases.
import createClient from 'microlink.io'
const microlink = createClient()
const screenshot = await microlink.screenshot('https://example.com')
console.log(screenshot.url)
The first argument is the page to capture. With no screenshot options specified, the SDK uses its documented defaults. The returned SDK object includes an asset URL and can include fields such as image type, width, height, and size. This example prints the hosted screenshot URL; it does not write the image to a local file.
Microlink’s Screenshot guide describes the underlying request in terms of two parameters: the target url and screenshot. The SDK is a convenience layer for that API rather than a separate capture format.
#1 Best Overall
Choose screenshot options for the capture
Pass options as the second argument to screenshot(). For example, request a full-page JPEG with quality set to 80:
const screenshot = await microlink.screenshot('https://example.com', {
fullPage: true,
type: 'jpeg',
quality: 80
})
console.log(screenshot.url)
| Need | Option | Behavior |
|---|---|---|
| Capture the visible viewport | Default | Captures the visible browser area rather than the full scrollable page. |
| Capture the full scrollable page | fullPage: true |
Extends the capture beyond the initial viewport. |
| Capture one visible page region | element: 'main' |
Targets the visible DOM element matched by the CSS selector. |
| Choose an image format | type: 'png' or type: 'jpeg' |
PNG is the documented SDK default; JPEG is also supported. |
| Set JPEG compression quality | quality: 80 |
Sets JPEG quality from 0 to 100; the documented default is 80. This setting is relevant to JPEG output. |
To capture a specific region, use a selector for an element that is present and visible on the page:
Rank #2
- Intuitive interface of a conventional FTP client
- Easy and Reliable FTP Site Maintenance.
- FTP Automation and Synchronization
const screenshot = await microlink.screenshot('https://example.com', {
element: 'main'
})
See Microlink’s SDK content methods reference for the documented screenshot options.
Use the returned asset or call the underlying API
Use the SDK result
The SDK result is an asset object. Use screenshot.url when your application needs the hosted image URL; use its other returned fields when you need metadata such as dimensions, type, or byte size.
Rank #3
Understand the raw HTTP response
The raw API uses a target url and screenshot=true. In its standard JSON response, the screenshot asset and metadata appear under data.screenshot, for example as a URL, dimensions, image type, and byte size. That nested API envelope is different from the SDK’s asset object, where the URL is available as screenshot.url. Consult the API screenshot parameter reference for API-level behavior.
When a screenshot-only task does not need page metadata, Microlink’s guide documents setting meta: false. If the caller needs a direct image response rather than the normal JSON envelope, the guide documents embed: 'screenshot.url'. Choose the normal response when your code needs screenshot metadata or the documented direct-image mode when it needs the image response itself.
Rank #4
Handle common integration problems
- The import fails: The example uses an ES module import. Run it in an ES module project, or adapt the module syntax to your project’s configuration and the package’s supported exports.
- The capture call rejects: Check that the target is a complete, reachable URL and inspect the error returned by the SDK. The documentation cited here does not establish a single cause or recovery for every API error.
- You expected a local file: The SDK returns a hosted asset URL and metadata; printing
screenshot.urldoes not download the image. Fetch that URL separately if your application needs a local copy. - The capture is shorter than expected: The default capture is the viewport. Set
fullPage: truewhen you need the entire scrollable page. - The output format or quality is wrong: Set
typeexplicitly. Usequalityfor JPEG compression; it is not a PNG quality control. - The selected region is missing: Confirm the CSS selector matches an element that is visible in the rendered page. The documented
elementoption targets a visible DOM element.
Access, compatibility, and performance considerations
Microlink’s guide says its API works without an API key and describes 25 free requests per day, but the guide does not date that quota. Treat it as a vendor-stated allowance rather than a guaranteed current limit; check the Microlink Screenshot API page for current access and plan terms before relying on it in production.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The documentation used here does not establish a Node.js compatibility range, and the code example was not independently executed. Confirm compatibility against the package information for the version you install. The product page also makes performance and isolation claims; they are vendor claims, not independently verified measurements in this article, so no speed or security guarantee is implied.
Best Value
Or skip the browser setup
If you need an HTTP call instead of running the Microlink SDK, ScreenshotNeo is a website screenshot API and MCP server. Its endpoint returns PNG, JPEG, WebP, or PDF output. Here is the documented cURL pattern, using Stripe as the target URL:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp
See the ScreenshotNeo documentation for API parameters. Before capture, it accepts cookie or consent banners as a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be turned off. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, with response headers reporting the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info, and capture_pdf for AI agents and other MCP clients. The free plan includes 1,000 shots a month with no card; paid plans start at $5 for 3,000 shots.
Sign up for ScreenshotNeo’s free plan: 1,000 screenshots a month, no card required.
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 glitchesFrequently Asked Questions
Does Microlink’s Node.js SDK save the screenshot as a local file?
No. The documented SDK result includes a hosted asset URL; download that URL separately if you need a local file.
What is the difference between Microlink’s SDK response and API response?
The SDK exposes an asset object such as { url, type, width, height, size }; the raw API places the screenshot object inside data.screenshot.
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.




