marly.studio

Last updated May 14, 2026

Help

A practical reference for using marly.studio, understanding what happens to submitted media, and knowing where billing, privacy, and support boundaries sit.

Quick paths

  • Review privacy and terms on the legal page.
  • Manage connected services, plan, quota, and billing in settings.
  • Contact support@marly.studio for account, privacy, billing, or stuck-job questions.

What marly.studio does

  • marly.studio turns long videos into short-form clips by transcribing the source, finding moments with strong short-form potential, and rendering downloadable Shorts-style outputs.
  • You can upload a video file or submit a supported source URL. URL import is best-effort because public platforms can block server-side downloads, remove media, geo-restrict access, or change their extractor rules.
  • Generated clip titles, descriptions, scores, transcripts, and playback links are shown in the job workspace so you can review before downloading or publishing.

Uploads and URL imports

  • Uploads are scanned, probed, and processed on the server. Very large uploads can take longer to validate before transcription starts.
  • URL imports use server-side media tooling. A successful metadata probe does not guarantee the provider will allow the final download.
  • If an import fails, retrying later can help, but repeated provider-blocked failures usually mean the source cannot be imported from the current server environment.

Processing and clip outputs

  • Jobs move through validation, transcription, analysis, extraction, upload, and completion stages. Active job pages update while work is running.
  • Local Whisper transcription is the default path. Remote transcription providers may be used under configured queue pressure, with local fallback when possible.
  • Smart reframing can crop, blur, split, or preserve framing depending on the source and detected layout. The goal is usable vertical output, not a guaranteed perfect edit.

YouTube publishing and automation

  • Connecting Google lets the app identify your YouTube channels after you approve the requested scopes.
  • Manual publishing only publishes clips you choose. Channel automation discovers new uploads from a connected channel and can process eligible videos on a schedule when enabled.
  • You can disconnect Google from settings. Disconnecting removes stored Google credentials and connected-channel records used by YouTube features.

Billing and optional support

  • Paid plans control quota and product access through Stripe subscription billing when billing is configured.
  • The optional support page is a one-time contribution flow. It does not change your plan, quota, access, or support level.
  • Billing portal, checkout, and webhook records are handled through Stripe; the app stores only the operational billing identifiers it needs.

Privacy and security

  • Workspace data is isolated by session or account. Signed media links are short-lived and served with private no-store cache controls.
  • Google refresh tokens are encrypted before storage. Session cookies are signed and use secure production cookie settings.
  • Operational logs and audit records are designed to avoid raw secrets, tokens, passwords, and full sensitive identifiers.

Troubleshooting

  • If a job is still active, leave the job page open or return later from the home dashboard.
  • If a source URL fails before download, try a direct upload of the original file when you have permission to use it.
  • For account, billing, privacy, or stuck-job help, email support with the job ID or account email you used to sign in.