How Much Does Loki Cost for Website Screenshot Testing?

Direct answer: Loki is presented by its project as an MIT-licensed tool for visual regression testing of Storybook stories. The reviewed project and integration pages do not state a Loki subscription or license price. That does not make the full workflow cost-free: teams may spend money on CI or compute, image storage, and maintenance, depending on their setup. The sources do not quantify those costs, so there is no supported universal monthly total.

What you pay for when using Loki

Loki captures Storybook stories, compares the screenshots with reference images, and reports visual differences. Its documented workflow includes installing Loki as a development dependency, configuring it, starting Storybook, capturing references, running comparisons, inspecting diffs, and approving new references when a change is intentional.

The license describes the software; it does not price the resources or time needed to run it. Your total depends on your project and chosen execution target:

Cost area	What to account for	What the reviewed sources establish
Loki license or subscription	Whether Loki itself has a stated purchase or subscription price	The project is described as MIT-licensed; no subscription or license price is stated.
Compute and CI	Local machines, CI minutes, or cloud execution	Execution targets include local Chrome, Docker, and AWS Lambda, among others. No typical compute or CI cost is given.
Image storage	Reference screenshots and current captures	Documentation describes screenshots stored in Loki project folders and recommends checking references into the repository; Git LFS is an option.
Setup and maintenance	Keeping Storybook, browsers, targets, and references working	The workflow requires configuration and a running Storybook server. The sources do not estimate developer time.

For an estimate, measure your own CI runtime and storage use, then apply your provider’s current rates. Include the time needed to maintain the target environment and review visual changes. A price for Loki alone cannot answer those questions.

How Loki’s screenshot workflow affects cost

Choose a target. The integration listing names Chrome in Docker, Chrome in AWS Lambda, local Chrome, iOS simulators, and Android emulators. Requirements differ by target; listed prerequisites include Node 16+ and optional Docker, GraphicsMagick, and Chrome for relevant configurations.
Start Storybook. Loki does not start it for you. The getting-started instructions require the Storybook server to be running and accessible.
Create references and run comparisons. Loki stores reference images and current screenshots in its project folders. Review diffs and update references only when the visual change is intended.
Decide where artifacts live. The documentation recommends checking reference images into the repository and mentions Git LFS as an option. This can affect repository and storage needs as the image set grows.

These are workflow costs to investigate, not a published price list. The reviewed documentation does not provide a typical monthly cost for CI, cloud compute, image storage, or developer time.

How to estimate your own monthly cost

Count how many visual-test runs your team expects per month, including pull requests, main-branch builds, and reruns.
Run the suite on your intended target and record its duration and any billable resources it uses.
Check how many reference and current images are retained, where they are stored, and whether repository storage or Git LFS affects your bill.
Apply your CI, cloud, and storage providers’ current rates to those measured quantities.
Separately estimate maintenance time for configuration, browser or simulator setup, and visual review.

This produces a project-specific estimate. It avoids treating “MIT-licensed” as a promise that CI, storage, and maintenance cost nothing.

Loki compared with a hosted visual-testing workflow

Storybook documents an official visual-testing integration powered by Chromatic, a cloud service. Its documentation says stories are sent to cloud browsers for snapshots and comparison. Loki’s documentation instead describes configurable execution targets, including local Chrome, Docker, AWS Lambda, and mobile simulators. These are different operating models; the reviewed research did not establish current Chromatic plan prices, so a numeric price comparison would be unsupported.

When comparing the workflows, check where rendering happens, what your team must configure and maintain, which browsers or platforms you need, how results fit into CI, and current verified pricing. Do not infer the cost of either option from the license or hosting model alone.

Or skip the browser setup

For individual website captures outside a Storybook visual-regression suite, ScreenshotNeo is a website screenshot API and MCP server for developers. Its API returns an image or PDF from one GET request. This is a separate capture workflow rather than a replacement for Loki’s reference-image comparisons. See the ScreenshotNeo API documentation.

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,
)
r.raise_for_status()
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}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
const image = Buffer.from(await res.arrayBuffer());
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', image));

ScreenshotNeo removes cookie banners, newsletter popups, and chat widgets before capture; those steps can be turned off. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed, and response headers report the page verdict and billing status. Its MCP server provides screenshot tools for Claude, Cursor, and other MCP clients. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 shots. Loki remains the relevant tool for comparing Storybook stories to visual references; ScreenshotNeo is for capturing websites through an API or MCP.

Create a free ScreenshotNeo account for 1,000 screenshots a month with no card.

Troubleshooting Loki cost and setup questions

Symptom or assumption	Likely cause	What to do
Loki appears unable to access stories	Storybook is not running or is not reachable at the configured address.	Start Storybook yourself and confirm Loki can reach it before capturing or comparing.
The team expects a published monthly Loki price	The reviewed project and integration material describes licensing and setup, not a subscription price.	Use the project’s license information for Loki itself; calculate CI, compute, storage, and labor from your actual setup.
A “free software” estimate omits infrastructure	An open-source license does not specify what a CI provider or cloud target charges.	Measure usage on the selected target and apply current provider rates.
Reference images make the repository large	Visual references are stored as project artifacts and may accumulate.	Review retention and repository storage; the documentation mentions Git LFS as an option.
A mobile or cloud target needs extra setup	Supported targets have different prerequisites and environments.	Check the integration requirements for the selected target, including optional Docker, GraphicsMagick, or Chrome dependencies where relevant.

FAQ

Does MIT-licensed mean Loki has no cost?

It describes the software license, not the complete cost of running and maintaining visual tests. The reviewed sources do not state a Loki subscription price or quantify operating costs.

Does Loki start Storybook automatically?

No. Its getting-started instructions say to start the Storybook server so Loki can access the stories.

Can I compare Loki and Chromatic by price from these sources?

No. The sources describe Loki’s execution options and Storybook’s Chromatic-powered cloud workflow, but do not verify current Chromatic pricing.

Are Loki’s reference screenshots kept outside the repository?

The documentation describes reference and current screenshots in Loki project folders and recommends checking references into the repository, with Git LFS as an option.