data-slots=image, heading, text
Hero image

Adobe Photoshop API - Firefly Services

Unlock the potential of Adobe Photoshop and cutting edge AI/ML services through an easy-to-use RESTful API.
data-slots=heading, text, button
data-variant=secondary
data-backgroundColor=background-color-gray
data-borderColor=#14b8a6
data-hasborder=true

🚀 Now Generally Available - Photoshop API v2

Photoshop API v2 is now generally available. This release introduces major improvements in scalability, flexibility, and programmability, enabling teams to build production-grade, high-volume content workflows. v2 addresses these gaps and introduces a more extensible foundation for modern content pipelines.

Overview

Welcome to the Adobe Photoshop API, now integrated into Firefly Services. Our API follows REST-like principles, utilizing standard HTTP response codes, verbs, and authentication methods that return JSON-encoded responses. While the examples provided are in cURL, feel free to develop your application in any preferred language.

This guide will assist you in:

Photoshop API v2 — General Availability

Photoshop API v2 is the unified next-generation surface for Photoshop and Lightroom-style workflows in Firefly Services: one architecture, consistent request and response patterns, and flexible output destinations. If you've worked with v1, you likely encountered limitations around file size, embedded assets, and rigid workflows. v2 addresses these gaps and introduces a more extensible foundation for modern content pipelines.

What's new in v2

Linked Smart Objects

Photoshop API v2 adds support for linked smart objects, a foundational improvement for content supply chains.

In v1, embedded smart objects created several challenges:

With linked smart objects:

This enables more efficient, maintainable, and scalable content systems.

Increased file size limits

This allows for significantly more complex documents and removes a key limitation for enterprise use cases.

UXP scripting (JavaScript automation)

Photoshop API v2 introduces support for UXP scripting, allowing developers to execute JavaScript directly within Photoshop workflows.

This adds a programmable layer to automation and unlocks advanced use cases:

Previously, these scenarios required custom workarounds or waiting for new API capabilities. With UXP scripting:

This significantly expands what can be built with the API.

More powerful action workflows

Richer document intelligence

Expanded creative control

Built for scale

Photoshop API v2 services

Many useful Photoshop operations are available in the v2 API. Here are just a few:

Explore all available services in the Photoshop API v2 guides or browse endpoints in the Photoshop API v2 reference.

Migration from v1

Photoshop API v1 will reach end of life on July 31, 2026. Teams should begin planning migration to v2 immediately to take advantage of the new capabilities and avoid service disruption.

To support a smooth transition, we provide topic-based migration guides covering edit, document, layer, actions, output, artboard, manifest, and status flows. Versioned /v2 endpoints and a dedicated v2 OpenAPI reference exist alongside the legacy v1 reference, so you can compare contracts and plan migration without merging the two.

Start your migration:

Discover

data-slots=heading, link, text

Get Started

Getting Started Guide
Get started with the Adobe Photoshop Firefly Services.
data-slots=link, text
Photoshop API v2 guides
Recommended. Migration guides, v1-to-v2 topics, and workflow guides for the v2 API.
data-slots=link, text
Photoshop API v2 reference
Recommended. Browse the OpenAPI reference for Photoshop API v2 endpoints.
data-slots=link, text
Tutorials
Explore our tutorials page for comprehensive guidance.
data-slots=link, text
Photoshop API v1 guides (Deprecated)
⚠️ Deprecated — End of life July 31, 2026. Migration to v2 is required. Reference only; do not use for new integrations.
data-slots=link, text
Photoshop API v1 reference (Deprecated)
⚠️ Deprecated — End of life July 31, 2026. Migration to v2 is required. Reference only; do not use for new integrations.