Dayvid FAQ

That depends on your Suno or Udio plan, not on Dayvid. Both tools grant commercial rights on songs generated while you held a paid subscription, and treat free-tier outputs as non-commercial. So if you intend to monetize, the track needs to have been generated under a paid tier, and you should keep records of the plan and date. Dayvid accepts the audio file and renders the video around it; it does not grant, change, or warrant the rights to your audio. Read the current terms on the generator's side before you publish.

Dayvid does not change your Content ID exposure either way. A Content ID claim happens when your track matches a registered audio fingerprint, which can occur with songs from any generator, especially ones generated on a tier that did not grant commercial rights. The protective pattern is the same regardless of the video tool: generate on a paid tier, keep the plan and date on record, and dispute with that evidence if a claim is wrong. Neither Suno, Udio, nor Dayvid offers a copyright warranty on outputs.

You bring the audio, so you are responsible for holding the rights to it, the same way you would be if you handed the track to any editor or upload tool. Dayvid renders the video from the audio and visuals you provide; it does not claim ownership of your track and it does not vet or clear your audio rights for you. The commercial-use rules sit on the music generator's side (your Suno or Udio tier), and the platform rules sit on YouTube, TikTok, and Instagram. Dayvid is the audio-to-video step in between.

Disclosure is the uploader's responsibility, and it is a deliberate per-upload choice on each platform, not something Dayvid sets silently. On the YouTube publish step, Dayvid sends the video to your channel as a private draft with metadata filled in, and you set the altered or synthetic content flag yourself before going public. For TikTok and Instagram, where you download and upload natively, you enable each platform's AI label in its own composer. Dayvid will not set or unset the disclosure flag on your behalf, because the platforms require the creator to make that call.

YouTube publishing is generally available: Dayvid uploads the rendered video to a connected YouTube channel through the official YouTube Data API, with title, description, and tags filled in, landing as a private draft you flip public when ready. Direct publishing to Instagram is built and validated but in limited rollout, not generally available, and direct TikTok publishing is not generally available. For those platforms today, the reliable path is to download the rendered MP4 from Dayvid and upload it natively.

Yes, a v1 REST API exists, in limited and gated rollout rather than fully self-serve. With a bearer token you can submit audio, create music videos and music highlights, poll jobs, manage projects, and publish, all programmatically. It is not a fully public GA developer product yet, and there is no SDK, public webhooks, or no-code (Zapier, Make) integration. The human-readable reference is at /docs/api, and the agent-readable canonical version is at /SKILL.md.

Dayvid accepts common audio formats, including MP3, WAV, FLAC, M4A, AAC, and OGG, up to 100 MB per file. You can upload your own file directly, or paste a Suno, Udio, or SoundCloud link as a shortcut input where supported.