Adobe Stock Sync connects your Adobe Stock Enterprise account with Frontify, automatically importing newly licensed assets into your DAM — including key metadata.This eliminates manual download and upload workflows and helps keep licensed assets organized and searchable in Frontify.
Requirements:
Enterprise Frontify account
Adobe Stock enterprise account
Overview
Many enterprise teams license creative assets through Adobe Stock while managing brand and campaign assets in Frontify.Without an integration, teams must manually download licensed files from Adobe Stock and upload them into Frontify. This can lead to:
Manual, repetitive workflows
Inconsistent tagging
Duplicate uploads across teams
Limited visibility into licensed assets stored in the DAM
Adobe Stock Sync streamlines this process by automatically importing newly licensed assets into Frontify on a scheduled basis.
How it works
A user licenses an asset in Adobe Stock.
The sync runs at a scheduled interval.
Newly licensed assets are automatically imported into Frontify.
Adobe Stock metadata is automatically added as tags in Frontify.
Assets appear in your configured destination folder.
No manual download or upload is required.
What gets synced
Included
Newly licensed Adobe Stock assets
Configurable license type filtering:
Standard
Extended
Video_HD
Video_4K
Metadata transfer (keywords and category are added as Frontify tags)
Configurable destination folder (library root or specific folder)
Scheduled sync interval (between 1 and 24 hours)
Not included
Real-time synchronization
Support for non-Enterprise Adobe Stock plans
Two-way sync (changes made in Frontify are not pushed back to Adobe Stock)
Sync frequency
The integration runs on a configurable schedule:
Default: every 12 hours
Minimum: every 1 hour
Maximum: every 24 hours
During each run, the system checks for newly licensed assets and imports them into Frontify.
Metadata mapping
When assets are imported, Adobe Stock keywords and category information are automatically added as tags in Frontify. This ensures assets are searchable and organized immediately after import.Additional metadata can be edited or enriched within Frontify after the asset has been synced.
Folder configuration
During setup, you can define where synced assets will be placed:
Library root
A specific folder within a library
All imported assets will appear in the selected location.
Permissions and asset ownership
Imported assets are uploaded into Frontify using a dedicated integration setup. Once imported, assets behave like any other asset in your library and follow your existing Frontify permission structure.
Integration setup
Part 1 - Adobe Stock project setup
Involve the necessary technical teams to set up an API project within your Adobe environment. You can find a step-by-step guide below for exactly what you need. If you want broader information directly from Adobe, here you go.
Head to the Adobe Developer Console.
Create a new project.
Rename the project to something meaningful, like Frontify Adobe Stock sync.
Add an API and pick "Adobe Stock".
Pick OAuth Server-to-server and add the Adobe Stock product profile. Select "Save configured API."
Download the OAuth Server-to-Server JSON and send it to us securely (or just grab the Client ID and Client Secret and send them securely).
Step 2 - Your Frontify setup
Once you’ve set up your Adobe Stock project and sent the credentials, we need to know a few specifics about your sync:
What library do you want to sync Adobe Stock assets to? (URL)
Do you want to place them in a specific folder? If so, send us the URL to the folder.
Do you only want to sync assets with specific licenses?
Enabling Adobe Stock Sync
Adobe Stock Sync requires initial configuration. To get started, contact your Frontify representative or Customer Success Manager. Our team will guide you through the setup process.
As a next step from our side, we'll set up a sync user (integration+customer@frontify.com) who must be invited to the library. This user must not be deleted or removed from the library – otherwise, the sync won't work anymore.