Build plugins for Atlas

The plugin platform lets you add real features to Atlas: windows, buttons, side panels, embedded browsers, and support for new file types. Plugins run inside the app behind a permissioned API, and you build their UI with any web framework.

Plugin Center

InstalledWindowFormatDevelopment

CivitAI BrowserSearch CivitAI, download models and LoRAs with trigger words and details.Installed

Pinterest Visual SearchVisual search from any Atlas image, and save the matches back to a folder.Installed

Reverse Image SearchSearch the web by image via TinEye, Yandex, or Google Lens.Installed

ConvertBatch-convert files to another format, organized into your library.Install

What you can build

A plugin adds one or more surfaces to Atlas. The CivitAI browser and Pinterest visual search that ship with the app are built on this same platform.

How they run

A plugin is a package: a manifest, an icon, and the code for what it adds. Its UI runs in a sandboxed frame and reaches Atlas only through the documented window.atlas API. That API is permissioned, so a plugin gets read, write, network, or process access only when its manifest asks for it.

{
  "schemaVersion": 2,
  "id": "com.you.my-plugin",
  "name": "My Plugin",
  "version": "1.0.0",
  "description": "What it does, in one line.",
  "author": "You",
  "visibility": "public",
  "kind": "window",
  "icon": "icon.svg",
  "host": { "launch": "local-window" },
  "entryPoints": { "window": "index.html", "overview": "overview.html" },
  "permissions": ["items.read", "log.write"],
  "compatibility": { "app": ">=0.9.0", "pluginApi": "^1.0.0", "platforms": ["win32"], "architectures": ["x64"] }
}

Next

Start with the Quickstart to build and sideload one in a few minutes. Then read Capabilities for every surface, the SDK reference for the full window.atlas surface, and Manifest for every field.