Back to blog

How to Create and Publish an OpenChatCut Community Resource

Choose a resource type, prepare an openchatcut-plugin@1 package, generate a real preview, and move through review to publication.

Jul 28, 2026OpenChatCutOpenChatCut
How to Create and Publish an OpenChatCut Community Resource

A shareable editing resource must answer three questions: What is it, what does it do to real media, and can another OpenChatCut installation load it reliably?

The community submission flow handles all three together. A creator uploads the original resource and preview inputs, the system renders a presentation from the actual resource, an administrator reviews the result, and users receive the same validated package.

Step 1: Choose the correct resource type

Choose a category by what the resource does, not by its visual style:

  • Motion graphics are editable titles, graphics, and information animations.
  • Sound effects are audio files that can be auditioned and downloaded.
  • Transitions are GLSL changes between two images.
  • Visual effects are shader passes applied to one image.
  • Zooms are camera movements described by a shape or key-point envelope.
  • LUTs are color treatments described by .cube data or a shader.

The category determines accepted files, size limits, required fields, and preview behavior. A package submitted under the wrong category will fail item-type validation.

Step 2: Prepare an installable package

Except for sounds, installable resources use an openchatcut-plugin@1 JSON package. The minimal shape contains package metadata and at least one item:

{
  "format": "openchatcut-plugin@1",
  "id": "creator.resource-name",
  "name": "Resource Name",
  "version": "1.0.0",
  "items": [
    {
      "id": "resource-name",
      "name": "Resource Name",
      "type": "fx",
      "frag": "..."
    }
  ]
}

Each item type adds its own payload:

TypeCore field
Motion graphiccode
Transitionfrag
Visual effectfrag
Zoomshape or envelope
LUTcube or frag

Keep identifiers stable. Increase version for a new release instead of creating a new resource ID for a copy change or new cover.

Step 3: Provide real preview inputs

Website previews are generated from the resource itself. Creators provide the inputs needed to make the result visible:

  • Motion graphics are rendered directly into a poster and complete animation.
  • Transitions use one start image and one end image.
  • Effects, zooms, and LUTs use one source image.
  • Sounds use the uploaded audio to generate playback and a waveform.

A useful source image has a clear subject, visible texture, and a reasonable range of light and shadow. It is not a separate advertising poster; it is test media that shows what the resource actually changes.

Step 4: Add authorship and licensing

The submission form also collects a name, version, creator, description, tags, and license. Available license choices include CC0 1.0, CC BY 4.0, MIT, and custom terms.

Add a source URL when the resource comes from a public project or requires attribution. The creator must also confirm the right to distribute the resource and preview media. This information stays with the listing so users can understand whether modification, redistribution, and commercial work are allowed.

Step 5: Validation, review, and publication

After upload, the system performs the first validation pass:

  1. Check the file type and size limit.
  2. Parse the package and validate required fields.
  3. Confirm that item.type matches the selected category.
  4. Record the file digest, metadata, and validation report.
  5. Store the original file and preview inputs.
  6. Move the submission into review.

An administrator can inspect the creator, original upload, validation report, and system preview. The result can be published, returned for changes, or unpublished. A demo video never replaces the resource itself; download and installation always resolve to the validated original package.

How users receive a published resource

Published resources appear in both the website catalog and the Discover tab inside OpenChatCut. Visual resources get an individual poster and hover playback, while sound effects keep their own audition control and waveform.

For installable resources, users can copy an install URL from the website or install from the Extension Center. The resource then appears in the local Installed list before it is added to a specific project.

Final checklist before submission

Use this short checklist before uploading:

  • The resource ID and item type are correct.
  • The package runs in OpenChatCut.
  • Preview inputs clearly expose the change.
  • The name and description are accurate.
  • The version matches this release.
  • Licensing and source attribution are complete.
  • The package contains no unrelated files or sensitive information.

When it is ready, open Contribute a resource and turn an effect that exists in one project into something other creators can keep editing.