Log in to Freesound

Problems logging in?
Don't have an account? Join now

Problems logging in?

Enter your email or username below and we'll send you a link to help you login into your account.

Back to log in

Almost there!

We've sent a verification link by email

Didn't receive the email? Check your Spam folder, it may have been caught by a filter. If you still don't see it, you can resend the verification email.

Default title

  • Sounds
  • Tags
  • Forum
  • Map
    • Sounds
    • Packs
    • Forum
    • Map
    • Tags
    • Random sound
    • Charts
    • Donate
    • Help

Freesound Forums

  • Freesound Forums
  • Freesound Project
  • freesound-attributor.py - New CLI tool to create attribution lists from your filesystem

freesound-attributor.py - New CLI tool to create attribution lists from your filesystem

Subscribe

Started February 14th, 2026 · 1 reply · Latest reply by Halleck 1 month, 1 week ago

Halleck

178 sounds

744 posts

1 month, 1 week ago Edited: 1 month, 1 week ago
#1

Hey all,

A long time ago I made a windows GUI app called the Freesound Attributor to scan a directory of files downloaded from Freesound to generate an attribution list. I have not maintained this tool but I still need a sort of tool to do this, so I made a new one which was much simpler to develop. It's an open-source, cross-platform command-line utility written in Python 3. As such it's not as user-friendly, but I tried to make it as easy as possible to install and use within this constraint. I think if you spend 15 minutes learning the command line with an online tutorial you could learn how to use this tool (and thousands more also.)

It has two modes, the default one is completely offline, the other scrapes Freesound for CC license links for each sample the user had previously downloaded to the directory it's looking at to add to the attribution file. Unfortunately I did not find the official API suitable for this simple use case as it does not seem to support unauthenticated usage and I didn't want to provide my own API key in a plaintext script, or have to have users each have to apply for their own API keys. If any of the Freesound devs have a suggestion for a different approach please let me know and I'll see what I can do.

Please see the README for more info.

If you try it out and have any feedback please let me know here or in a GitHub issue.

Enjoy!

Freesound Admin Emeritus | Official Acclivity Fan Club Member | Stuck with FLAC? Check the FAQ.
Post reply
About Freesound Terms of use Privacy Cookies Developers Help Donations Blog Freesound Labs Get your t-shirt!
© 2026 Universitat Pompeu Fabra