Klippy

Features not included

The editor focuses on fast, private, in‑browser workflows. To keep the product lean and portable, a number of professional or server‑heavy capabilities are intentionally out of scope. This page lists what is not included and suggests alternatives when relevant.

Collaboration and cloud

  • No multi‑user real‑time editing or cursors.
  • No cloud project storage/sync or user accounts — projects live in the browser (IndexedDB). Export/import JSON or bundles to move work between machines.
  • No built‑in team sharing, commenting, or review links.

Editing scope

  • No keyframe graph editor or per‑property animation curves.
  • No motion tracking, masking editor, rotoscoping, or planar tracking.
  • No nested timelines/sequences and no multi‑cam sync.
  • No full audio workstation: multichannel mixing, compressors/EQs/effects chains are not included (basic volume only).
  • No global clipboard for arbitrary items across projects; use Duplicate (D) and timeline tools instead.

Color management and codecs

  • No ACES / color‑managed pipeline or HDR grading; export is SDR.
  • No LUT management or professional scopes (waveform, vectorscope, parade).
  • No hardware HEVC/AV1 encoding; MP4 export uses H.264, WebM uses VP8/VP9.
  • Alpha in MP4 is not supported (by codec). Use WebM alpha (Transparent tab) or export ProRes 4444 in custom pipelines.

Server‑side pipelines

  • No built‑in server render farm or queue. All exports are client‑side.
  • Remotion Lambda is not bundled — it is documented as an optional integration for heavy jobs (see Rendering > Server rendering).
  • No automatic cloud ingest or streaming inputs.

AI features

  • No on‑device Whisper transcription; the provided route proxies a worker/service you configure.
  • No large model hosting in app; /api/ai is a secure proxy to your provider.
  • No automatic translation/dubbing pipeline (beyond what your external services provide).

Platform and packaging

  • Browser‑first; no native installers. An Electron starter may exist for experiments but is not a supported product build.
  • No mobile app store packaging; mobile support targets in‑browser editing/export only.

Interchange and pro workflows

  • No EDL/FCPXML/AAF interchange import/export.
  • No VST/OFX plugin host.
  • No timecode burn‑in/generator or reel metadata export.

What to use instead

  • Heavy/cloud renders: integrate a Remotion Lambda renderer and export project bundles to S3.
  • Advanced grading/codecs: export intermediates and finish in a dedicated NLE/color tool.
  • Collaboration: store .klippy.bundle.json files in your VCS or cloud drive and gate merges via PRs/reviews.