Overview

Explore Demos

Get Started

Ways to Open the Editor#

You can initialize CE.SDK in several ways depending on your content pipeline:

• Start with a Blank Canvas
  Create new content from scratch by defining the canvas dimensions manually or programmatically.

• Load a Scene
  Restore a saved scene from serialized scene data, a scene file, or a self-contained archive.

• Create from Media
  Initialize the editor with a preloaded image or video.

• Create from Template
  Kick off the editor with a predefined template, including placeholders and editing constraints.

• Import a Design
  Import external designs with the relevant importer, then load the resulting scene or archive in the SDK.

Set the Zoom Level#

After a scene is open, use Set Zoom Level to control the viewport and focus the canvas on the content your user should inspect next.

Using Low-Quality / High-Quality Assets#

To ensure responsive editing and high-quality exports, CE.SDK allows you to dynamically switch between asset resolutions:

• Edit with Low-Res Assets
  Load smaller versions of images or videos during the editing process to reduce memory usage and improve performance.

• Export with High-Res Assets
  Swap out low-res placeholders for full-quality assets just before exporting. This can be handled using the Scene or Block APIs by switching asset paths or making use of source sets for fills.

Working with Watermarked or Placeholder Media#

CE.SDK supports licensing-based workflows where full-resolution assets are only available after purchase or user action:

• Use Watermarked or Preview Media on Load
  Start with branded, obfuscated, or watermarked assets to limit unauthorized use.

• Swap with Purchased Assets Post-Checkout
  Replace asset URIs within the same scene structure using a one-time update, ensuring consistency without disrupting layout or styling.

Implementing a Custom URI Resolver#

Use URI resolver APIs to intercept and customize asset loading:

• Why Use a URI Resolver?
  Handle dynamic URL rewriting, signed query parameters, asset migration, CDN fallbacks, or redirects to internal mirrors.

• How It Works
  The engine routes every asset URI through your custom resolver function. This function returns the final, resolved URI used for the current fetch operation.

• Recommended Use Cases:

  • Append signed query params
  • Redirect public assets to internal mirrors
  • Refresh tokenized URLs before they expire