Polotno SDK lets developers connect custom asset libraries — images, icons, videos, fonts, or brand elements in numerous ways. You can disable default assets and expose your own collections, connect APIs, or manage internal repositories so users can drag and drop approved assets into their designs. All asset data and metadata are accessible through the schema, so every selected asset is automatically stored with its unique identifiers and URLs. This makes it easy to manage brand consistency, track asset usage, and automate content generation.
Key features
Custom data sources
Connect any source of media — from a CDN, DAM system, or internal API. You control asset visibility, access rules, and filtering logic. Implementation is fully flexible: you can build it as a custom tab in the side panel, open it as a lightbox modal triggered by a button, or even insert assets through a floating overlay, custom drawer, or command palette.
In practice, you can design the interaction flow however you want — browse, search, drag, replace, or bulk-insert — since the SDK only requires you to define how assets are fetched and placed on the canvas.
Branded asset collections
Organize icons, logos, backgrounds, or templates into categorized collections. You can define libraries by project, team, or brand to ensure users always select the correct version of each element.
Search and tagging
Add searchable metadata like tags, categories, or descriptions to help users find the right asset instantly. The SDK supports server-side or local search logic depending on how your assets are served.
Format flexibility
Libraries can include multiple formats — PNG, JPG, SVG, MP4, or JSON-based templates. The editor handles all supported file types and maintains full visual fidelity across them.
Access control
Limit asset visibility by user role, subscription plan, or team. Integrate your existing authentication and permissions logic with the SDK to create gated or premium asset sets.
Automation and schema integration
Each inserted asset is defined within the project schema — including its source, type, and metadata. This enables programmatic asset replacement, automated creative generation, and synchronization with external systems.
Example use cases
Brand platforms – Provide approved logos, icons, and templates to maintain design consistency across teams.
Marketing builders – Offer image and video libraries filtered by campaign or client.
E-commerce tools – Give sellers quick access to brand-approved backgrounds and product frames.
AI content apps – Feed generated visuals or logos into a custom library automatically via API.
Print and packaging systems – Manage production assets, dielines, and texture patterns from internal storage.
Enterprise creative hubs – Connect internal DAM systems or S3 buckets for secure asset access.
Developer benefits
Plug-and-play integration with custom APIs or storage.
Unified schema for all asset types — image, video, or SVG.
Full control over permissions, filtering, and organization.
Compatible with self-hosted or cloud-rendered deployments.
Commercial-safe licensing for SaaS and enterprise products.
FAQs
Can I connect my own API as a source?
Yes. You can feed custom endpoints directly into the asset picker and define your own filtering or pagination logic.
Does it support internal or private libraries?
Yes. Assets can be fetched from authenticated endpoints or private storage buckets.
Are asset selections stored in the schema?
Yes. Every asset reference includes source, ID, and metadata for reproducible rendering.
Can users upload new assets?
Yes. You can allow uploads or restrict access to read-only libraries depending on your setup.
Does it work with both image and video assets?
Yes. The same library architecture supports all major file types, including vector and motion assets.