Polotno SDK was designed to be molded into your product — not the other way around. Every part of the editor can be extended, restructured, or replaced to fit your design system, workflow, and business logic. From UI panels and asset sources to authentication, rendering, and branding, you can adapt Polotno into a seamless part of your platform while keeping the simplicity of one schema and one editor. The SDK provides both extensibility (deep control over features and appearance) and integration hooks (ways to connect your backend, auth, or database). Together they allow you to create a white-label creative platform with the depth of a design system and the speed of an API integration.

Extensibility

Custom controls

You can add, replace, or remove UI controls across the editor surface — sidebar buttons, toolbar items, canvas context menus, floating panels, and layer controls — without forking the core. Controls are plain React components that you register with the SDK and bind to built‑in commands or your own custom actions.

• What counts as a "control": any interactive UI element that triggers a command or opens a panel, including buttons, toggles, dropdowns, sliders, inputs, and menu items

• Where you can place them: sidebar sections, top toolbar, object toolbar, right‑side properties, canvas context menu, and modal or floating panels

• How they connect: call Polotno commands, dispatch your own business logic, or emit events for analytics and automation

• Safety: controls run in a sandboxed extension layer, so upgrades of the SDK don't break your code as long as you target stable APIs

Examples: "Generate Ad Variant," "Insert QR Code," "Lock Brand Font," "Send to Print," or a role‑based "Approve" action that writes back to your backend

Custom panels

Polotno supports modular side panels that can be completely replaced or extended. You can build panels for brand assets, project libraries, AI assistants, or integrations with external tools. Each panel connects to the same project schema, ensuring all changes are saved, exportable, and automatable — see panel patterns in the Docs.

Custom asset libraries

You can connect any media source — images, icons, fonts, or templates — from your CDN, DAM, or API. Polotno doesn't limit you to the default picker; you can build your own asset tabs, lightboxes, or pop-ups that load data dynamically. It's the same approach used for integrations with Unsplash or custom brand repositories; see editor configuration in the Docs and recommended upload behavior. For deeper control, see custom asset libraries.

Theme and branding

The editor can match your product's identity completely. Adjust color palettes, icons, typography, and layout spacing. Replace the default logo and splash screen or embed the editor within your own UI shell. White-labeling is total — users never know it's Polotno underneath.

Source code access

For almost all cases, customization through API and components is enough. Polotno is minified by default, and the public SDK covers everything required for integration. For legal, compliance-driven cases or heavy core customization cases, Enterprise clients can license source code access under a separate, one-time agreement.

ㅤ

Integration

Authentication and user management

Polotno SDK doesn't handle authentication internally — you bring your own. Integrate your login system, tokens, or SSO provider and use Polotno's event hooks to load or save projects per user. You can also define granular user roles, permissions, or quotas using your existing identity logic. Learn more about authentication and user management.

Database and storage

You can sync project data with your own backend or storage system. Polotno's JSON schema ensures that every project can be stored, versioned, or restored without format loss. Designs can be pulled from or pushed to any database, CDN, or file service — storage options and schema are covered in the Docs.

API and state sync

Polotno provides callbacks and event hooks for saving, updating, and tracking changes in real time. Use these to trigger external workflows — for example, autosaving edits to your backend, syncing templates across accounts, or kicking off render tasks on completion. For workflow-level control, see automation and design workflows.

Event hooks and automation

Hooks and callbacks allow full programmatic control over the editor lifecycle: track user actions, listen for element changes, trigger AI prompts, or synchronize design states across multiple clients. This makes it easy to embed Polotno into complex business systems without building custom editors from scratch.

Custom development services

For complex deployments, the Polotno team offers implementation assistance — from setting up asset management to customizing UI, scaling rendering, or building full white-label solutions.

ㅤ

Customization examples

• Replace default image picker with a brand asset library connected to your API

• Add a "Generate social post" button that runs a script on the canvas

• Customize the sidebar to only show features relevant to your audience

• Apply your theme colors and typography so the editor feels native to your app

• Sync user templates and drafts with your internal template library — explore templates

• Integrate AI systems to auto-generate dynamic designs or tag content directly within Polotno — try AI text

ㅤ

Summary

Polotno SDK is built around one idea — full creative control without touching the core code. You can extend panels, define logic, integrate your stack, and rebrand the entire UI while keeping one consistent editor experience. Whether you're embedding it into a SaaS platform, eCommerce product, or enterprise design system, Polotno adapts entirely to your environment, not the other way around. For adjacent capabilities, see image editing, animations, canvas editor, shapes and icons, and export.