Send approved images to websites and Microsoft 365, use the library from Canva and Chrome, import from other systems, and build on the REST API, webhooks and MCP.
A Team or Business label marks the lowest plan that includes a feature; the others are on every plan, Free included.
An administrator connects the Microsoft 365 tenant and selects images with conditions, for example a field set to Approved or a collection. Freedam checks each image's usage rights before sending it, sends new and edited images within minutes and withdraws removed ones. Nothing is stored in SharePoint.
Create one channel per website, with conditions that select the images and the use and territory where they will appear. Each image gets links that do not expire, up to a chosen largest size, with an optional watermark. Rights are checked on every request, so an image whose rights expire stops showing.
Each Canva user connects their own Freedam account from the Apps sidebar, then browses collections or searches the workspace and adds an image or video with a click or a drag. The panel applies the same permissions as the Gallery: assets the user may not download cannot be added to a design.
Install Freedam for Chrome from the Chrome Web Store and sign in once. The side panel searches assets and collections, narrows results to images or videos, and lets you copy an image, download a file or drop it into the page, with the same permissions as in the Gallery.
Data sources connect to a WebDAV server such as a NAS or a Perfion export, an S3 bucket or Google Drive. An optional CSV or XLSX catalog maps columns to metadata, vocabularies and collections, and a test run or dry run shows the result before files are imported.
A source can refresh every hour, every 6 hours, daily, weekly, monthly or on a cron schedule. Each refresh downloads only what changed: changed files get a new version, removed files are archived by default, and files with no matching SKU are listed for review. Google Drive sources refresh by hand only.
Administrators create application tokens with scopes, and a token can never do more than its owner may. The v1 endpoints cover assets, collections, uploads, metadata, shares and webhooks, each token gets 60 requests per minute, and a playground in the administration area runs test requests.
Install @freedam/sdk from npm. The client has typed methods for assets, collections, shares, metadata, operations, embeds, tokens and consents, retries network errors, 429 and 5xx responses while honoring Retry-After, and handles pagination.
Register an HTTPS endpoint through the API and pick events for assets, collections, shares, uploads and workflow status changes. Each request is signed so you can verify it, failed deliveries are retried up to 5 attempts in total, and an endpoint that keeps failing is switched off.
Asset responses include signed image URLs for each width from 128 to 5120 pixels. The server returns AVIF, WebP or JPEG depending on what the client accepts and checks the user's preview, download and watermark rights on every request. The URLs expire after one to two hours.
The Embed button under a video gives an HTML snippet with a size, start time and options such as autoplay, muted and loop. Anyone with the code can play the video without signing in. It works only when the video's rights policy allows publishing, and the API returns the same codes.
The MCP Server page gives the endpoint URL and setup steps for Claude and ChatGPT. Each assistant uses an API token, and the token's scopes and its owner's role decide which tools it may run: search, asset details, uploads, metadata updates and collection changes.
Start free · 30 days of paid features · No card
Create a workspace, upload a few hundred assets and see how search, sharing and approvals work for your team.
