Nimbus Screenshot Extension vs. Nimbus Capture: What Is the Difference?

Short answer: Nimbus Screenshot and Nimbus Capture are not presented by the vendor as two separate competing products. The vendor says Nimbus Clarity and Capture were brought together under the Nimbus Capture name. Nimbus Screenshot is the older name associated with the browser extension; the current Capture offering includes an updated browser extension and a separate desktop version. The vendor says older versions may still work, but will not be upgraded or supported, and recommends downloading the updated versions.

The practical choice is whether you need the browser extension for webpage screenshots and annotation, or the separate desktop app for desktop capture workflows. The available product pages do not establish full feature parity between those versions.

What is the difference between Nimbus Screenshot and Nimbus Capture?

Question	Nimbus Screenshot	Nimbus Capture
Name and status	Older name associated with the screenshot browser extension.	Current name used for the updated capture offering after the vendor united Nimbus Clarity and Capture under Nimbus Capture.
Where it runs	Browser extension.	Updated browser extension and a separate desktop version.
Typical tasks described by the vendor	Webpage screenshots, full-page or selected-area capture, and annotation.	Screenshot and video recording software; the extension product page also describes microphone and webcam options for recording.
Support	Older versions may remain usable, but the vendor says they will not be upgraded or supported.	The vendor recommends using the updated extension and desktop versions.

This is mainly a naming and version question, rather than a comparison between two unrelated tools. The vendor’s pages describe the extension and desktop app separately, but do not document that every feature is available in both.

Is Nimbus Screenshot now Nimbus Capture?

In the vendor’s current naming guidance, Nimbus Screenshot is the older extension name and Nimbus Capture is the name used for the updated product. The vendor also says Nimbus Clarity and Capture were united under Nimbus Capture. So if you see “Nimbus Screenshot” in an older guide or installation, it may refer to the older extension rather than a separate current product.

That naming history does not prove that every old extension has automatically changed into a current one, or that an existing installation has been updated. Check the installed extension’s version and the vendor’s current download page before relying on it.

Is Nimbus Capture a browser extension or a desktop app?

It is presented as both: an updated browser extension and a desktop version. The browser extension is described for webpage capture and annotation, including full-page and selected-area screenshots. The product page also describes screen recording with microphone and webcam options. The vendor’s download center lists a desktop app for Mac and Windows, but that listing may be dated; confirm current platform support on the vendor’s download page before installing.

Which version should you choose?

Choose the browser extension when your work is centered on capturing pages in the browser and annotating them.
Consider the desktop version when you need a desktop-installed capture application. Verify its current operating system support and features with the vendor.
Do not assume feature parity. The available pages do not confirm that every recording, screenshot, or annotation feature works identically in the extension and desktop app.

Do you need to update the old Nimbus Screenshot extension?

The vendor recommends downloading its updated browser extension and desktop version. It says previous versions can still be used, but will not be upgraded or supported. That is the vendor’s stated guidance; it is not a guarantee that a particular old installation still works in your browser or operating system.

Check the extension name and version in your browser’s extension manager.
Open the vendor’s current download page and confirm which extension and desktop builds are offered now.
Review the permissions requested by the current extension and decide whether they fit your use case.
If you rely on saved captures or annotations, confirm where the updated product stores them and whether your existing workflow carries over before removing the old version.
Install the version that matches your workflow, then make a sample capture and verify the result.

Do not use an old support article to infer current prices or plan limits. The historical support page in the research describes past Capture Pro features and an old relationship with Nimbus Note, but does not establish current pricing, plan names, or entitlements.

Privacy when saving captures to Nimbus Note

The Mozilla Add-ons listing says that when screenshots are saved to Nimbus Note, system data such as the operating system version and browser data such as the browser version are also sent. This detail is specific to that save-to-service workflow. The listing may be dated and does not establish what data is transmitted by every current version or when captures are saved locally. Check the current extension’s privacy information and permissions for the exact behavior you need to assess.

When a screenshot API is a better fit

If you need screenshots inside a script, backend service, or AI-agent workflow, an API can avoid installing and maintaining a browser extension on each machine. For that use case, try ScreenshotNeo first: it removes cookie banners, popups, and chat widgets before capture, and only clean shots are billed.

ScreenshotNeo is a website screenshot API and MCP server. It accepts a URL in one GET request and can return PNG, JPEG, WebP, or PDF. Its MCP tools let Claude, Cursor, and other MCP clients take screenshots, get page information, and capture PDFs. It is an alternative for automated website captures, not a replacement for a desktop screenshot application.

Or skip the browser setup

Make a GET request to capture a page. This cURL example saves a WebP file:

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

Equivalent Python:

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
    timeout=90,
)
r.raise_for_status()
open("shot.webp", "wb").write(r.content)

Equivalent Node.js using the built-in fetch API:

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
await Bun.write('shot.webp', new Uint8Array(await res.arrayBuffer()));

For Node.js versions without Bun, save the response with the built-in filesystem module:

import { writeFile } from 'node:fs/promises';

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
await writeFile('shot.webp', Buffer.from(await res.arrayBuffer()));

See the ScreenshotNeo API documentation for request options. Cookie banners, popups, and chat widgets are removed before the shot; bot checks, blank pages, and failed loads are never billed. Its MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots a month with no card, and paid plans start at $5 for 3,000. Sign up for 1,000 free screenshots a month.

Troubleshooting and common questions

The old extension still appears, but I cannot find the same name in the store

The product naming has changed. Start from the vendor’s current download page and look for the updated Nimbus Capture extension instead of relying on an old bookmark or guide. Confirm the publisher and requested permissions before installing.

My old version still opens. Does that mean it is supported?

No. The vendor says older versions may still be used, but will not be upgraded or supported. Continued operation on one browser does not establish future compatibility or support.

Does the desktop app include every extension feature?

The sources reviewed do not establish feature parity. Check the current feature list for the specific desktop build and test the workflow you depend on before migrating.

Can I rely on an old Pro feature or price mentioned in a help page?

Not as a current entitlement. The available Pro information is historical and does not verify present plan names, pricing, or limits. Check the vendor’s current pricing and plan details.

Does saving locally send the same data as saving to Nimbus Note?

The Mozilla listing’s data note applies to saving screenshots to Nimbus Note. It does not establish the data flow for local saves or every current product version. Consult the current privacy details for the exact build and save destination.

Sources

Nimbus Capture product and migration information (vendor source).
Nimbus download center (vendor source; confirm current platform details there).
Nimbus product information (vendor source).
Mozilla Add-ons listing for Nimbus Screenshot (privacy detail scoped to saving to Nimbus Note).