Upload AI-made sound to Freesound or Pixabay: tags and labels
Freesound allows generative AI sounds with a GenAI tag and the model named; Pixabay wants an AI-generated checkbox. How to record the model from a Sume job.

Both sites accept AI-made audio, with conditions. Freesound's FAQ says AI generated audio "is permitted as long as it is marked with the GenAI tag and the model is indicated". Pixabay's terms require an upload to be marked with its "AI-generated" checkbox. Neither rule says anything about whether your tool's output may be uploaded; that is a separate question for the tool's own terms.
How do the two sites compare?
Their rules are short, so the table covers them all.
| Rule | Freesound | Pixabay |
|---|---|---|
| AI-made audio allowed? | Yes, with conditions | Yes, with conditions |
| How to mark it | GenAI tag | "AI-generated" checkbox |
| Name the model? | Yes, the model is indicated | Not stated in the terms we read |
| Real people, artists, brands | Not stated in the FAQ section we read | Cannot be used as tags; no mimicking artist styles or reproducing protected material |
| Reuse preferences for AI training | Uploader panel: no preference, Open Source Models only, Non-Commercial Open Source Models only, or No generative AI | Not stated in the terms we read |
Where do you find the model name from a Sume job?
A Music Router job echoes the id you requested in job.model, so sume/music-auto stays sume/music-auto. The engine that actually ran is in job.request.routed_model, for example lyria-3.5, on both the router and the Music 1.0 routes. That is the value to type into a model field. Keep the whole job result with the file so you can show what produced it.
Is there a watermark to know about?
Google's Lyria 3.5 page says all generated audio includes a SynthID audio watermark, imperceptible to the human ear. Sume's Music Router runs Lyria 3.5 today, so a track from it may carry that mark; you do not add anything on top. It is a provenance signal, not a license.
What should you check before you upload?
Uploading publishes the file for others to reuse, so check these first:
- Whether your plan and the engine's terms let you publish the output under a public license.
- That the title, tags and description do not name a real artist or brand, which Pixabay prohibits as tags.
- That the prompt did not ask for a named artist's voice; Google says Lyria's safety filters block that request.
- That the model name you enter matches
routed_modelon the job.
Is it a good idea to upload generated sound at all?
It can be useful: a labelled, model-named upload gives others something to reuse and gives you a public record. It also commits you to the library's rules and means anyone can reuse the file under the library's license. If the track is a client deliverable, ask the client first. If it is a generic effect, a loop or an ambience, uploading is low risk once the checks above pass.
Keep the original job result and your prompt. If a moderator asks how the sound was made, you can answer with facts.
What does a Freesound uploader choose about AI training?
The FAQ describes a preferences panel with four choices: no additional preferences, Open Source Models only, Non-Commercial Open Source Models only, or No generative AI. If you upload a generated sound, think about which you want; you are publishing it into a library that others can use as training or reference material.
Sources
Related posts
More in Use cases
- Use a trending TikTok as a reference for an original YouTube Short
Study a trend without re-uploading it. Sume's trending search returns TikTok metadata, not video files, which fits YouTube's Oct 2026 originality push.
- VAST video ads: Microsoft wants 500, 1200 and 2500 kbps files
For third-party VAST video, Microsoft Invest recommends three bitrates and 15 or 30 s on Google inventory. What a Sume master gives you and what it lacks.
- Veterans Day 2026 tribute: a silent photo slideshow with caption cues
Veterans Day is Wed, Nov 11, 2026. Build a respectful, silent tribute from employee-provided photos with caption cues and a Timeline join, with consent first.
- Google Ads video action campaigns: 10 s minimum, three ratios
Google's spec page gives video action campaigns a minimum length of 10 seconds in 16:9, 9:16 and 1:1. Cut a master to length and ratio with Sume.
Written by Sume