RVE Partners with Lots of Sounds for Royalty-Free Audio
React Video Editor has partnered with Lots of Sounds to bring 1,500+ royalty-free sound effects and music tracks into modern video workflows, with 20% off for RVE users.
Sam
Creator of RVE
Most web video editors have a decent story for clips, captions, and exports.
Audio is usually where the workflow falls apart.
Users leave the editor, browse stock sites, download files, drag them back in, then figure out whether the license is actually safe for commercial use. If you are building a product on top of RVE, that is exactly the kind of friction that makes the editing experience feel unfinished.
That is why we partnered with Lots of Sounds.
They provide a royalty-free audio API with 1,500+ sound effects and music tracks, and RVE users get 20% off with code RVE20.
Key takeaways
- This partnership gives RVE users a cleaner way to add royalty-free audio without sending people out to stock sites.
- Lots of Sounds is API-first, which makes it a much better fit for embedded editors, automated workflows, and AI-assisted products.
- You can now link readers from this announcement into a practical implementation guide and related RVE architecture posts.
Why this partnership makes sense
The thing we liked about Lots of Sounds was not just the catalog.
It was the shape of the product.
Most audio libraries are still designed like media marketplaces. They work if a person wants to manually browse a website, but they are awkward if you want audio to behave like part of your application.
Lots of Sounds feels different:
- the library is accessible through a proper API
- the licensing is CC0 and commercially safe
- search is fast enough to work inside a UI
- the results are structured enough to work in automated flows
That maps closely to how RVE is used in practice. A lot of teams are not just building a simple timeline anymore. They are building AI video apps, content generation pipelines, and product workflows where audio needs to be searchable, previewable, and insertable without context switching.
If this is you
- You are embedding video editing into a SaaS product and need sound effects inside the same workflow.
- You are building AI video generation or agent-driven editing, and audio needs to be selected programmatically.
- You want a royalty-free sound effects API without attribution headaches or unclear licensing.
What this gives RVE users
Inside a modern React video editor, audio should not feel like an afterthought.
This partnership makes it easier to build flows where users can:
- search for sound effects and music in the editor
- preview before adding anything to the timeline
- fetch audio through a predictable API
- avoid licensing uncertainty
That is the practical value.
If you want the implementation side, read How to Add Sound Effects to a React Video Editor. That post goes deeper into the API surface, example requests, preview flows, and how to add downloaded audio to timeline state.
Why the API-first angle matters
This is the part that matters most if you are building productized editing, not just a demo.
With a file-based workflow, audio stays manual:
- someone has to find the sound
- someone has to download it
- someone has to upload or import it
- someone has to check whether usage is allowed
With an API-based workflow, audio becomes part of the application layer.
That means you can build:
- search and preview directly inside your editor UI
- backend-assisted asset fetching
- templated workflows that attach audio automatically
- LLM or agent tools that request sounds with natural language
If you are already thinking in those terms, React Video Editor for AI Video Apps is the closest companion post.
What makes Lots of Sounds a strong fit
- API-first access instead of a manual stock-library workflow.
- CC0 licensing, so there is no attribution or commercial-use ambiguity.
- Fast search and signed delivery that fit real product experiences.
- A natural fit for AI workflows, tool calling, and agent-driven selection.
What you still need to build
- You still need to decide how audio search, preview, and insertion work in your editor UI.
- You still need to handle where API keys live: on the user side or through your backend.
- You still need timeline and project-state logic that knows how to place downloaded audio.
Why this is useful for AI video workflows
More RVE users are building products where the first draft is generated automatically and then refined by a human.
In that setup, audio needs to be more than a folder of files. It needs to be queryable.
Lots of Sounds is useful here because it supports the kind of structured access AI systems need:
- natural language search queries
- predictable endpoints
- machine-readable docs
- an OpenAPI spec for reliable tool integration
That is much better than asking an LLM to scrape random stock sites and guess what is safe to use.
If your team is still working through the broader editor shape, How to Build a Video Editor in React is still the best higher-level starting point.
What is in the library
The catalog covers the common audio categories teams usually need for web-based editing:
- nature and weather
- UI and interface sounds
- foley
- music
- cinematic transitions and impacts
- ambient backgrounds
That range matters because most products do not need one kind of sound. They need a practical baseline library that can cover product demos, social clips, explainers, AI-generated edits, and template-based workflows.
Pricing and offer
Lots of Sounds currently offers:
- Pro at $15/month
- Enterprise at $49/month
Both include unlimited downloads, and RVE users can use RVE20 for 20% off.
Getting started
- Sign up at lotsofsounds.com/sign-up
- Pick a plan
- Use code RVE20
- Generate an API key
- Add search, preview, and import flows to your editor
Questions readers usually ask
Next step
Add royalty-free audio to your RVE workflow
Use the partnership discount, then follow the implementation guide to wire search, preview, and audio insertion into your editor.
Final thought
This partnership is useful because it solves a very specific problem that shows up in almost every serious editor workflow: audio is important, but the sourcing flow is usually clunky.
Lots of Sounds makes that part more programmable.
For RVE users building modern editing products, that is the part worth caring about.
