Troubleshooting

Honest answers to the problems people actually hit. If yours isn't here, the Jobs panel error text on a failed job is the best first clue.

Activation

My device code is rejected. Check the format: codes look like XXXX-XXXX, and the field uppercases for you. Make sure you copied the whole code from Account > Devices at kitly.fun, and that the seat isn't still bound to another machine. If you've replaced a computer, release the old seat first (on the old machine under Settings > Device > Release this device, or from your account on the site).

Is there a trial? No. Kitly has no trial mode; the activation card stays until a valid code is entered.

Generation

Generate does nothing, or fails immediately. Nine times out of ten this is a missing or invalid API key for the operation's provider. Check the operation's execution chip and endpoint, then Settings and the matching provider tab. The Run a test job button in the Jobs panel confirms the plumbing works at all. See Connect providers.

An operation shows an amber chip. It runs on Fal right now, but a local model is available. Click the chip to open Settings and download the model if you'd rather run it on your machine.

My generation finished but I don't see it. If you selected something else while it ran, look for the "N new outputs" strip above the Generate button and click it. Completed jobs in the Jobs panel also select their output when clicked.

Video

A video won't play in the viewer. Kitly's own outputs are web-optimized and play everywhere, but imported footage can arrive in formats the player can't decode. Fix it in place: right-click the video, choose Re-encode..., pick H.264, and use the new asset. See Video tools.

Every video tool fails the moment I open it. FFmpeg isn't installed, or Kitly can't see it. Kitly doesn't bundle FFmpeg; it runs the copy on your machine. Open Settings and check the FFmpeg section: Not found confirms it. Install it (one command, see Set up FFmpeg) then click Re-check, or click Locate FFmpeg... if it's installed somewhere unusual.

Kitly says my FFmpeg can't encode H.264. Some builds, mostly minimal Linux packages, ship without it. Kitly uses your graphics card instead where it can, and only stops when there's no way to encode at all. Install a build listed as "full" on the FFmpeg downloads page and point Kitly at it. See Set up FFmpeg.

My trim points aren't exact. You used Fast mode, which stream-copies and snaps to keyframes. Rerun with Accurate (the default) for frame-exact cuts.

Tracking

The camera solve fails on my shot. First suspect: no parallax. A pan or tilt from a tripod can't be solved, because nothing in the frame shifts against anything else; the solver says so with a clear message. This limitation is physics and applies to all matchmove software. Use a planar or point session for 2D work on tripod shots. If the camera does translate and the solve still fails or drifts: delete tracks stuck to moving objects or reflections, raise the confidence threshold, and set intrinsics to manual if you know the lens (or calibrate for the FOV).

The solve worked but the scale is wrong in Blender. Solve scale is arbitrary until anchored. Add a reference measurement on the Calibrate tab (pick an axis, enter a real-world length) and export again.

The camera drifts on a long clip. Kitly does no bundle adjustment, so error accumulates over long ranges. Track and solve the section you actually need.

Extract frames does nothing, or fails straight away. Frame extraction runs on FFmpeg, which you install yourself. Check the FFmpeg section in Settings; if it says Not found, that's your answer. See Set up FFmpeg. Sessions started from an image sequence skip extraction and aren't affected.

Object tracking finds nothing. The Object session needs a detection model. Click Download recommended model (YOLOX-Nano, Apache-2.0) in the session, or register your own YOLO ONNX under Settings > Local Inference. Also check the class filter chips; your subject may be detected but filtered out of view.

One person became three targets. Occlusions split tracks. Select the fragments (Ctrl click or lasso) and Merge, then Fill gaps for the internal holes. See Object tracking.

Mocap

The capture is jittery or loses the performer. Markerless single-camera capture depends on the source. Keep the full body in frame, light evenly, avoid heavy motion blur and occlusion. On video sources, raise Refine passes. And judge the result against the synced source footage in the viewer before blaming the retarget.

Assistant

The Assistant won't respond. It needs a key for its selected provider (OpenRouter, Google, OpenAI, or Anthropic). Check the provider tabs in Settings, and remember OpenRouter can ride on your Fal key via Use Fal for OpenRouter.

App behavior

I closed Kitly but it's still running. That's by design. Closing the window hides it to the tray and jobs keep running. Quit for real from the tray icon's Quit or the burger menu's Exit Kitly. See Install.

Kitly won't open a second window. It's single-instance. Launching again fronts the existing window.

Where's autosave? There isn't one, and you don't need it: every change writes to disk as it happens. The exception is workflow graphs, which have an explicit Save (Ctrl+S) and save automatically before every run.

Updates never appear on my Mac or Linux machine. Auto-update is Windows only. Download new builds from kitly.fun. See Updates.

The onboarding modes list doesn't match the app. Sharp eyes: the tour's modes step shows five cards, while the nav has seven modes. Tracking and Storage exist; the tour just hasn't caught up. Their docs are here and here.