Storage, connected accounts, costs, and the things people ask before connecting a channel.
On your own server, in the data directory the install configures. Source videos, proxies, and rendered clips are files on that machine. Nothing is copied to any storage this app does not run.
Two things, both only when you use the feature that needs them. Transcription and clip scoring send audio and short transcript windows to the model provider configured in Settings. Publishing sends the finished vertical clip, its title, and its description to the platform you scheduled it for.
Your source video is never uploaded to a platform. Only the short you approved is.
YouTube, Twitch, and Kick, by URL or by watching a channel with Hunter. You can also upload a file directly, which is the reliable path when a platform blocks a download.
YouTube, TikTok, Instagram Reels, and X. Twitch and Kick are import sources only — neither offers a publishing API this app can use.
YouTube supports native scheduling, so a scheduled video sits private on your channel until its time. The others have no scheduling API, so xClipping holds the post on your server and uploads it at the chosen moment.
Only if you ask it to. A clip stays in the library until you queue it. Auto-publishing exists for Hunter watch targets, is off by default, and has to be enabled per target by choosing publish destinations.
Encrypted on your server, and used only to publish to the channel they belong to. They are never displayed in the app and never sent anywhere except the platform that issued them.
Channels page, inside the signed-in studio. Disconnecting deletes the stored tokens. You can also revoke access from the platform's own account settings — xClipping notices on its next attempt and marks the channel as needing reconnection.
It proposes which moments are worth clipping and drafts a title and description. It does not choose when to post, which account to post to, or whether to post at all. Boundaries, captions, layout, and copy are all editable before anything renders.
The app is self-hosted, so the running costs are your server plus whatever the transcription and scoring models charge. The Analytics page reports spend per stage, per model, and per source, so the cost of a given video is visible rather than inferred. Local transcription is supported and reports zero cost.
No. xClipping is deliberately a single-operator workspace: one account exists, and the database enforces that. There are no teams, roles, or shared access. Running it for a second person means running a second instance.
How it works covers the pipeline in more detail, and Support has the contact address.