Loki’s project describes it as an MIT-licensed visual regression testing tool for Storybook, but the reviewed project pages do not state a Loki subscription or license price. That does not make running tests cost-free: CI or compute resources, image storage, setup, and maintenance can add costs that depend on your configuration.
What Loki does—and what its license tells you
Loki captures screenshots of Storybook stories and compares them with reference images to flag visual changes. Its documented workflow involves installing Loki as a development dependency, initializing configuration, starting Storybook, creating references, running tests, reviewing image differences, and approving updated references when a change is intentional. Loki’s project pages describe the tool as MIT-licensed.
The MIT license statement is not the same as a published promise that every part of operating a visual-testing workflow costs nothing. The reviewed sources do not give a Loki subscription or license price, nor do they quantify typical infrastructure or developer-time costs.
What can add to the cost of running Loki?
Loki’s integration information lists several execution targets: Chrome in Docker, Chrome in AWS Lambda, local Chrome, iOS simulators, and Android emulators. These are configuration choices, not a price list. Your costs depend on the target, your existing infrastructure, and how your team stores and maintains its screenshots. The Storybook integration listing names Node 16+ as a prerequisite and Docker, GraphicsMagick, and Chrome as optional dependencies for relevant targets.
#1 Best Overall
- Execution: Local Chrome may use existing development or CI machines; Docker, Lambda, and mobile simulators involve different setup and resource choices. The sources do not quantify their costs.
- CI and infrastructure: Whether a run consumes paid CI minutes or cloud resources depends on where and how you run it. No typical cost per run or month is established.
- Reference images: Loki’s documentation describes storing reference and current screenshots in Loki folders in the project, and recommends checking reference images into the repository. Git LFS is an optional storage approach; the documentation does not state a storage cost. Getting started · Configuration
- Team time: Installation, configuration, triaging visual diffs, and maintaining references take effort, but the sources do not quantify it.
So there is no well-supported universal monthly total to quote. To estimate your own cost, identify the execution target, CI or cloud resources, screenshot-storage arrangement, and expected maintenance effort, then apply the prices for your chosen infrastructure.
How Loki’s workflow affects the estimate
Loki does not start Storybook for you: its getting-started instructions say you must start the Storybook server so Loki can access your stories. That means a cost estimate should include the environment that serves Storybook during capture, as well as the test runner itself. Loki’s getting-started guide also describes creating and storing reference screenshots in the project, which affects how a team handles versioning and storage.
Rank #2
Before choosing Loki, decide whether your team wants to configure and operate its own capture workflow, including its reference-image process, or use a hosted visual-testing approach. These approaches shift work and infrastructure in different ways; the available sources do not establish a current price comparison.
How Loki compares with Storybook’s hosted workflow
Storybook documents an official visual-testing integration powered by Chromatic: stories are sent to cloud browsers for snapshots and comparison. Loki instead documents configurable execution targets, including local and infrastructure-based options. Storybook’s visual-testing documentation describes the hosted workflow, but a current Chromatic plan price was not established here. Compare where captures run, what your team must operate, target support, CI integration, and verified current prices before deciding.
Or skip the browser setup
If you need screenshots of pages rather than visual regression testing of Storybook stories, ScreenshotNeo is a website screenshot API and MCP server for developers. A GET request can return an image or PDF. For example, this cURL request captures a page as WebP:
Quick Recap
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo API documentation for the request options. Before capture, it can accept cookie or consent banners and remove more than 60 known consent platforms, newsletter popups, and chat widgets; each cleanup step can be turned off. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and responses identify the page verdict and billing status in headers. Its MCP server provides take_screenshot, get_page_info, and capture_pdf for Claude, Cursor, and other MCP clients. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000.
Sign up for ScreenshotNeo’s free plan.
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.
