There's no support desk behind Swara Sound - this page is it. Most things that go wrong have a one-line answer below.
Check three things, in order:
Best in a Chromium-based browser - Chrome, Edge, Brave, or Opera. Generating and playing songs works everywhere, but choosing a local folder for your library only works in Chromium browsers, because it relies on a File System Access API that Firefox and Safari haven't implemented.
On Firefox, Safari, or mobile browsers: everything still works if you set Library storage to Google Drive instead of "this computer" (Settings → Song library storage). If you try to pick a local folder in an unsupported browser, Swara Sound now tells you so directly instead of the button silently doing nothing.
ACE-Step doesn't run on our servers - it runs on a GPU pod you deploy on RunPod, under your own account. That pod has to actually be running (not stopped, not still booting) for a generation to reach it. Before every ACE-Step run, Swara Sound pings the pod directly to check - if that ping fails, nothing was charged and nothing was sent.
Fix: go to Settings → "Deploy & manage your RunPod pod" and press Redeploy. A fresh pod can take a couple of minutes to finish booting before it answers - the hint under the provider dropdown on Create/Batch will tell you once it's reachable.
The Library page trusts an index file (library_index.json) it keeps inside
whichever folder you picked in Settings. If you picked a different folder than the
one you generated into, or a folder that already had audio files from somewhere else
(like the desktop app), those won't show up automatically the first time - but pressing
Refresh on the Library page now also scans the folder for any audio files not yet
in the index and adds them.
If songs are still missing: check Settings → "Song library storage" shows the folder you expect, and that you're consistently using the same storage mode (local folder vs. Google Drive) rather than switching between them.
Yes - see the full Privacy & Terms page, but the short version: your keys and bands live in a hidden folder in your own Google Drive, your songs live on your own computer or a normal Drive folder you control, and every generation request is relayed straight through to the provider using your key, never logged. There's no database on our end for any of it to sit in.
Suno (via kie.ai) - most consistent vocal quality, simplest to start with, priced per song.
Mureka - usually the cheapest per song of the two hosted options, generates multiple takes per request.
ACE-Step on your own RunPod pod - only worthwhile if you're generating a lot and want to pay GPU-time rates instead of per-song, or want a model you can fine-tune later. It also needs the extra setup of deploying and managing a pod yourself.
Each option shows its own live cost estimate on the Create page once you've added a key, so you can compare before generating.
No. Swara Sound is an independent interface that talks to their public APIs using keys you provide and pay for directly. Any trademarks belong to their respective owners.
Usually not. Swara Sound has no servers of its own doing the actual music generation - Suno, Mureka, and RunPod each have their own uptime, entirely outside our control. If something fails, check the provider's own status first before assuming the site is at fault: kie.ai, platform.mureka.ai, or RunPod's status page.
Swara Sound is currently an early, invite-only build while it's being shaken out - the banner at the top of the homepage says so for a reason. There's no signup form yet.
Revoke Swara Sound from your Google Account permissions page and, if you want, delete the "Swara Sound" folders from your Drive yourself. Nothing is left behind on our end, because nothing was ever stored there.