FAQs
Frequently Asked Questions
The common questions people ask before they trust a workflow with real audio files, metadata, releases, and turnaround-sensitive work.
FAQ
Useful answers before you commit a workflow to the page.
Are the tools only for musicians?
No. The platform is also useful for podcast editors, spoken-audio teams, release managers, content teams, and anyone who works with media files, timing, metadata, captions, or production math.
Do I always need to upload files?
No. Many tools are intentionally blended. If you already know the values, manual mode is usually faster. If the job depends on the media itself, upload mode gives you the stronger path.
Which formats are accepted most often?
Most audio tools accept common formats like MP3, WAV, FLAC, M4A, AAC, OGG, OPUS, and AIFF. Where a tool expects text, spreadsheets, captions, or artwork instead, the form explains that clearly in the upload guidance.
Can I download the processed output?
Yes. When a workflow creates a new file, the result panel exposes a direct download item instead of forcing you to rerun the tool or copy text from the page.
Are the AI tools always using the OpenAI API?
No. AI helper pages default to quick local drafting first. The paid AI path only runs when you explicitly switch to AI Studio, and the system rate-limits and caches repeated requests to control abuse and cost.
How should I report a tool issue?
Use the support or contact page and include the tool URL, the exact input you used, the file format, and the result you expected. That makes it much faster to reproduce the issue accurately.
Can I rely on the results without checking them?
For everyday workflow acceleration, yes, the tools are meant to be practical. For release-critical metadata, contracts, or delivery requirements, you should still review the output before publishing or signing off.
Where should I start if I am new to the catalog?
Start on the Explore or Tools pages, choose the category that matches the job you need to finish, and then open the full category page rather than jumping between unrelated tools.