How can we help?

Click "Start free" on the Studio landing page and sign up with Google or an email and password. No credit card is needed. Every new account starts with 20 free credits, enough to analyze 20 full tracks and see the complete output before you spend anything. Your account works across the website and the desktop app, and everything you analyze is stored in your account library, so you can switch devices freely.

The left sidebar is your command center: • Overview: your dashboard with analysis KPIs, genre and BPM charts, top tags, insights and achievements. • My Library: connect your real music folders and see every file as Tagged or Untagged. • New batch: where you add tracks and start an analysis run. • Active batch: live progress of the run currently analyzing. • Results: the full metadata table for the finished run, with inline editing and exports. • History: every batch you have ever run, organized into folders. • Integrations (API · MCP · Zapier): create API keys, connect AI assistants (Claude, Cursor) and analyze tracks programmatically (docs at tracktag.me/developers). • Settings: preferences, naming rules, sounds, alerts and your custom taxonomy. Below the tabs you will find your achievement progress, account card and credit balance with a Buy credits button. The avatar menu (top right) holds your profile, a switch to the Lab, credit purchases, settings and sign-out.

TrackTag has two workspaces: • The Lab (tracktag.me) is the single-track studio: deep-dive one song at a time, with AI descriptions, track-name ideas, sticky notes and session management. Lab analyses use your Lab plan (Free or Pro). • Studio (tracktag.me/studio) is the batch desk: up to 100 tracks per run, a permanent account library, folder-level tagging of your catalog and marketplace exports. Studio runs on one-time credit packs, separate from the Lab plan. The same account signs into both, and the avatar menu lets you jump between them ("Move to Lab" / "Open Studio").

The fastest route from zero to a finished export: 1. Open New batch and drag a handful of audio files in (or click to browse). 2. Keep the default field groups selected. You can trim them later. 3. Press Start. The run moves to Active batch; you can leave the tab and it keeps working. 4. When it finishes you land in Results: every track with BPM, key, genres, moods, description and tags. 5. Fix anything inline (click any field to edit), then hit Export and pick a format. Your batch is saved to History automatically. It will still be there next week, on any device.

Three ways to load tracks into a batch: • Drag and drop files, or an entire folder, anywhere onto the New batch drop zone. • Click the drop zone to browse and multi-select files. • From My Library: select untagged tracks (or a whole folder) and press "Analyze untagged": they are queued into a new batch automatically. Supported formats: MP3, WAV, AIFF, FLAC, M4A, OGG and AAC. A single run can hold up to 100 tracks; larger catalogs simply run as several batches. Duplicates are flagged before you start, so re-dropping the same folder never double-charges you.

The field selector is split into two lanes, and it is also how you choose what a batch costs. Included in Core (1 credit per track): BPM, musical key, mode, time signature, genres, mood, energy, the instruments you can hear, and your searchable keyword tag list. File details (format, duration, sample rate, bit rate, size) are read from the file itself and are always free. Ultra (2 credits per track): everything in Core plus the full written description, subgenres, emotions, atmosphere and themes, vocal type/gender/style, danceability, acousticness, complexity, song structure, tempo feel, dynamics, rhythm, melody, harmony, production style, era, influences, recording and mixing notes, and sync occasions. Both tiers run the same engine on the same audio and are equally accurate. The tier decides how many fields come back, never how good they are. Ticking any Ultra chip switches the batch to Ultra and the price updates before you start; Back to Core clears them. Your selection can be saved as a preset.

Every run gets a name. That is how you will find it in History and your library. Studio suggests one automatically (based on your naming pattern in Settings: date, folder name, or a running number), and you can type over it. Good habit for labels: name batches after the release or the client ("Vol. 3 Masters", "SyncPitch: Cinematic Pack"). Search in History matches batch names, folder names and even the tags inside results.

Press Start and Studio begins analyzing. Core costs 1 credit per track and Ultra costs 2, and the price is the same whether the file is a 90-second demo or a 9-minute mix. A 40-track batch is 40 credits on Core, 80 on Ultra. The exact figure is shown on the Start button before you commit. If your balance cannot cover the batch, Studio tells you before anything runs; nothing is ever charged mid-run as a surprise. Failed tracks (unreadable or corrupted files) are reported and refunded automatically, and cancelling a batch refunds every track that had not been processed yet.

The Active batch tab shows the run in real time: a progress bar, the track currently being analyzed, per-track status ("Analyzing track…" → done), and a running count. Finished tracks flip to green with their headline results (BPM, key, top tags) appearing as they land. You do not need to babysit it. Move to another tab, or minimize the window. The run continues in the background and a sound plays when the batch completes (you can turn the sound off in Settings).

Leaving the Studio tab open in the background is safe: the batch keeps processing. Closing the tab entirely pauses what has not started yet; already-finished tracks are saved to your library, and you can re-queue the rest. A Stop control ends the run early: everything analyzed so far is kept and charged, everything not yet analyzed is not. If a file fails (corrupted audio, unsupported codec inside a valid extension, zero-length file), the row is marked failed with a reason, you are not charged for it, and the rest of the batch continues unaffected.

Results is a spreadsheet-style view of the finished batch: one row per track, one column per field. The headline columns (BPM, key, genre, moods, tags) are visible immediately; expand a row to see everything the run returned. An Ultra row shows all 35 fields, including the written description, mixing notes, structure, influences and occasions. A Core row shows its 9 fields, and the Ultra-only ones are still listed underneath, greyed out with a small lock, so you can see exactly what you would gain by upgrading that track. Each track row has a play button (streams the original audio right in the table), a copy button per field, and a copy-all for the keyword tag list, handy when you are pasting into a store form one track at a time.

Ran a batch on Core and now want the description and the deep fields for one track? You do not have to pay twice. Open the track (or right-click its row) and choose "Re-analyze on Ultra". Because you already paid 1 credit for the Core scan, the upgrade costs 1 credit (the difference), so the track ends up costing exactly the 2 credits it would have cost on Ultra from the start. A confirmation shows the price before anything happens. There is also an "Upgrade batch to Ultra" button that walks a whole batch, skipping tracks that are already Ultra. This is a real re-analysis, not a lookup: the audio is sent to the engine again and scanned on all 35 fields, so it takes around half a minute per track. The file therefore has to be reachable: if it lives in a folder you have not connected in My Library, connect it first. Your work is never overwritten. The upgrade only fills in fields that are empty. Anything already on the track stays exactly as it is, including every value you corrected by hand, and your keyword tags are only ever added to, never removed or reordered. Tracks analyzed before upgrades existed cannot have their original charge verified, so those cost the full 2 credits. The confirmation always tells you which case you are in.

Click any value in the table to edit it in place: fix a genre call, tighten a description, add or remove tags. Edits save to your account library instantly and are what all exports use, so a correction made once is correct everywhere: in History, in My Library matching, and in every file you export afterwards. Tag fields have a dedicated editor: type to add, click to remove, and your tag-case rules (upper/lower/title) plus any prefix/suffix from Settings are applied automatically.

Every track gets a full written description, the paragraph a sync library or store listing expects. The description card has its own copy button, and the track title (taken from the file name) is prepended automatically so the paste is listing-ready. If a description misses the vibe, click it and rewrite any part. Your wording is kept from then on.

Inside a track's detail view, Studio surfaces other tracks from your own library that sit in the same sonic space: same tempo region, overlapping genres and moods. Use it to build alternates lists ("if you liked this cue, these three also fit") or to spot near-duplicates across old batches.

Every finished batch is saved to your account library on our servers, not just in the browser. Sign in on a different computer, or in the desktop app, and your whole history is there: every batch, every result, every edit. History shows each batch with its name, date, track count and summary. Open any batch to get the full Results table back, re-edit fields, or export again in a different format, months later, at no extra credit cost.

Create folders to group batches: by artist, by client, by release, by store. Each folder has a name and a color, batches can be dragged between folders, and the folder tree is saved to your account. Do not want to file things by hand? The "Auto-file by genre" action reads each unfiled batch's dominant genre and drops it into a matching folder in one click.

The search box in History (and My Library) matches batch names, folder names, track titles, genres, moods and tags across your entire catalog. Type "phonk" and every phonk-tagged batch and track surfaces, whatever it was named. Sort by newest, oldest, name or track count. Autocomplete suggests batch names, folders and tags as you type.

Rename a batch any time. The change syncs to your account instantly. Deleting a batch removes it from your library and from every device; the confirmation step tells you how many tracks are inside so nothing large disappears by accident. Deleting a batch does not refund credits (the analysis work already happened) and does not touch your audio files. Studio never modifies the files on your disk.

My Library turns Studio into a file manager for your actual music folders. Press "Connect folder/s" and pick where your music lives: your bounces folder, masters drive, sample packs. Studio scans it (subfolders included) and lists every audio file it finds. The scan is local and private: your files are never uploaded during a scan. Studio only reads names and sizes to build the index; audio leaves your machine only when you explicitly analyze a track. In the browser this works in Chrome, Edge and Brave on desktop. In the desktop app it works with the native folder picker, and connected folders stay connected permanently.

Every file in your connected folders is matched against your analysis history by name. Tracks you have already analyzed show as Tagged, with their BPM, key, genre and moods pulled straight into the table. Everything else shows as Untagged. That single view answers the question every catalog owner has: "how much of my library still needs metadata?" The Tagged/Untagged counts sit at the top, per folder and for the whole library.

Press "Analyze untagged" (on the whole library or scoped to one folder) and Studio queues every untagged file into a new batch. Review the queue, see exactly how many credits it will take, and start. This is the catalog backfill workflow: connect the folder, see 400 untagged, run them (or run them in chunks), and watch the folder turn green.

The library index is cached, so My Library opens instantly. Press Sync to rescan your folders and pick up new bounces, renamed files and deletions. Auto-sync (on by default) refreshes the index in the background when you open the tab. If a folder shows as disconnected in the browser, one click re-grants access (Chrome asks for permission again after a restart, which is a browser rule, not ours). In the desktop app folders never disconnect.

If a track exists in your results but its file moved on disk, the row shows as unattached. The Locate action opens a folder picker, scans it for the exact file (or the closest name match), and re-links it. Playback and library matching work again without re-analyzing anything.

The All-tracks view is customizable: toggle columns (length, BPM, key, genre, mood, size, status), sort by any of them, and switch between flat and by-folder layouts. Long ugly folder paths can get a display alias ("D:/Audio/2019_masters_final2" → "2019 Masters"), and folders you do not care about (stems, old demos) can be hidden from the view without disconnecting them.

Everything local (connected folders, the file index, cached history) is stored per account. If two people use Studio on the same computer, each sees only their own folders and results; switching accounts automatically clears the previous user's cached data from view. Server-side, every account's library is isolated by design.

Overview is your studio at a glance. Pick a range (Today, 7 days, 30 days, Year, All time, or a custom window) and every card follows it: • Tracks analyzed, credits spent and batches run, each with a trend sparkline. • What you make: a genre donut of everything you analyzed in the range. • Top tags: your most frequent moods and keywords, ranked. • BPM distribution: where your catalog lives on the tempo map. • Analysis activity: a six-month heatmap of your working rhythm. • Latest activity: a feed of recent batches, edits and exports.

Three smart cards read your data and talk back: • Insight spots patterns ("Electronic is your signature: 27% of everything you analyzed this month") with a jump to those exact tracks. • Weekly digest compresses your week into one line: batches, tracks, top genre, failures. • Suggestion recommends the next useful action: file unfiled batches, analyze a cold folder, or export a batch you finished but never shipped. Cards refresh with the range you pick and disappear when there is nothing worth saying.

The progress card under the sidebar tracks catalog milestones: first batch, 100 tracks, 500 tracks, streaks and more. They are cosmetic, but they make a 5,000-track backfill feel like a campaign instead of a chore.

The Overview cards can be reordered and hidden: keep the charts you look at daily on top, hide what you never use. Your layout is remembered on the device.

A preset captures a complete batch configuration: which field groups are on, which individual fields are excluded, and your tag-formatting rules. Save one per destination ("AudioJungle", "Pond5", "Label metadata sheet") and applying it configures the next batch in one click. Presets are saved to your account, so they follow you across devices and into the desktop app.

Different stores want different tag formats. In Settings you can force every generated tag to lowercase, UPPERCASE or Title Case, and add a fixed prefix or suffix (some libraries namespace tags like "mood:dark"). The rules apply during analysis and when you edit tags by hand, so the format never drifts.

If your organization uses its own vocabulary (a fixed genre list, an in-house mood scale), the taxonomy editor in Settings lets you map Studio's output onto it. Renames apply everywhere: results, library matching and every export. Your taxonomy is part of your account and rides along in exports so downstream systems see your terms, not ours.

From Results (or any batch in History) press Export and pick: • XLSX: a real spreadsheet, one row per track, one column per field. The workhorse for labels and library submissions. • PDF: a formatted, human-readable report. Good for clients and A&R. • XML: structured data for systems that ingest it. • TXT: plain text, one track per block. Paste-anywhere. • JSON: full machine-readable metadata, including every field, for developers and pipelines. Exports are generated from the current state of the batch: every inline edit you made is included.

Before the file generates, the field picker shows every column with a checkbox. Untick what the destination does not want: a store that only takes BPM, key, genre and 20 tags gets exactly those, in a clean file, with no manual spreadsheet surgery. Your selection is remembered per format, and presets can carry it too.

You do not have to export whole batches. Select specific tracks in Results (or across your library) and export just those, useful when a client asks for "the three cinematic ones" out of a 60-track run.

A Core analysis costs 1 credit per track and an Ultra analysis costs 2, flat, regardless of file length or format. Credits are one-time purchases, not a subscription, and they never expire. Buy a pack, use it over a week or over a year. Your balance is always visible in the sidebar. Every new account starts with 20 free trial credits. Credits are only consumed by successful analyses: failed files are refunded automatically, and re-opening, re-editing or re-exporting old results is always free.

Packs (one-time, credits never expire): • Starter: $20 for 50 credits. Test a real slice of your catalog. • Studio: $89 for 250 credits. The most popular for working producers. • Producer: $149 for 1,000 credits. A full catalog backfill for most artists. • Professional: $499 for 5,000 credits. Label and library scale. Per-track that runs from $0.40 down to $0.10, typically 60–78% cheaper than enterprise tagging platforms. If you tag continuously at volume, look at Unlimited-BYOK instead.

Press "Buy credits" in the sidebar (or the avatar menu → Purchase credits), pick a pack and pay by card. Payments are processed by Stripe: card details never touch our servers. Credits land in your balance the moment payment confirms, mid-batch if needed. Invoices and receipts come from Stripe by email, and your purchase history is available in the credits area.

When your balance dips below what a queued batch needs, Studio tells you before starting and shows exactly how many more credits the run requires. The GIFT badge next to the balance opens occasional promo credit codes. If you have one, redeem it there.

Credit packs are one-time purchases and are final: we do not refund credits, in full or in part, except where a refund is required by applicable law. Credits have no cash value and cannot be exchanged for money or moved between accounts. They also never expire, so an unused balance is not lost. It is simply waiting for your next batch. What does come back, automatically and always as credits rather than money: a track that fails to analyze, and every unprocessed track in a batch you cancel. Both land back in your balance within moments and are listed in your credit ledger. For anything else billing-related (a double charge, a payment that did not land, invoice details, VAT), write to us via the support page and include the email address on the Stripe receipt. We can trace every purchase on our side and we answer quickly.

Studio Unlimited-BYOK is the flat-rate plan for heavy taggers: $49/month (or $490/year, two months free). Instead of credits, you connect your own Google Gemini API key and run unlimited batches at any scale. Google bills your key for its own usage directly; we never charge per track. It is built for labels, sync libraries and producers who ingest new music continuously: at ~1,000+ tracks a month it beats any credit pack.

In Settings → Unlimited-BYOK, paste your Gemini API key (created free at Google AI Studio). The key is stored locally on your device for your account only: it is not synced to our servers, and switching accounts on a shared machine clears it. Once connected, batches run through your key automatically and your credit balance is untouched. If the key hits Google-side quota limits, Studio shows the error clearly and you can resume when the quota resets.

The desktop app is the same Studio (same account, same credits, same library) wrapped in a native Mac/Windows app with one killer advantage: a permanent My Library. Connect your music folders once and they stay connected forever, with no browser permission prompts and no risk of losing your library by switching browsers. You also get a real dock/taskbar presence, native menus with shortcuts, and a window that is always your Studio, no tab to lose.

Download the DMG, open it and drag TrackTag Studio into Applications. The app is signed and notarized by Apple, so it opens without security warnings on macOS 12 and later (Apple Silicon). On first access to protected folders (Documents, Desktop, Downloads) macOS asks once for permission. Click Allow and your library scans normally from then on.

Download the installer (.exe) and run it. Windows SmartScreen may show an "unrecognized app" notice on new releases: click "More info" → "Run anyway". The installer creates Start-menu and desktop shortcuts and you pick the install location.

Press Sign in and the app opens your default browser at a secure sign-in page. Sign in there (Google or email) and click "Open TrackTag Studio". The browser hands you back to the app, which shows a brief "Signing you in…" screen and lands you in your Studio, fully signed in. This browser handoff exists because Google blocks OAuth inside embedded app windows, so signing in via your real browser is both required and safer. The handoff link is one-time and expires in 60 seconds.

The native menu bar gives you: New Batch (Cmd/Ctrl+N), Go → Studio (Cmd/Ctrl+1) and the Lab (Cmd/Ctrl+2), zoom controls, fullscreen, and Help → Contact Support which opens the support form. The app always loads the current version of Studio on launch: web updates reach you automatically, no reinstall needed. New versions of the app shell itself are announced in-app and on the site.

Zapier links TrackTag to the apps you already use (Google Sheets, Dropbox, Airtable, Notion, Gmail, Slack) without writing anything. Two common setups: • Analyze in Studio, file it automatically. Every track you analyze in Studio can add a row to a spreadsheet, a page in Notion or a message in Slack, the moment it finishes. • Analyze automatically from a folder. New file lands in Dropbox or Google Drive → TrackTag analyzes it → the metadata goes wherever you want. Setup takes a few minutes: search for TrackTag in Zapier (it is listed in the public app directory) or use the button below, pick the TrackTag trigger or action, and paste an API key from Studio → Integrations. It works on any Zapier plan, including the free one. What you get to work with: a trigger ("Analysis Finished"), an action ("Analyze Track") and a lookup ("Get Analysis"). Every result arrives with BPM, key, genres, mood, instruments and the description as separate fields you can map one by one, plus ready-made "Summary line" and "Full report" fields if you just want a tidy email or message without building a layout. Analyses cost the same credits as everything else: 1 per track on Core (9 fields, tags included), 2 on Ultra (all 35). Build and test the whole thing free by connecting a test key (tt_test_…) first: it returns sample results and never spends credits.

TrackTag ships an MCP server, the standard that lets AI assistants use external tools. Once installed, your assistant can analyze tracks by itself: drop an MP3 into the chat, say "analyze this track with TrackTag", and the full metadata sheet comes back in the conversation. It can also find audio files on your computer by name, check your credit balance, and list recent analyses. Install in Claude Desktop: 1. Create an API key in Studio → Integrations and copy it. 2. Claude Desktop → Settings → Developer → Edit Config. 3. Paste the config block from the Integrations tab (it has a Copy button) and add your key. 4. Quit Claude Desktop completely (Cmd+Q) and reopen. 5. Drop in a track and ask. Analyses cost the same credits as Studio (1 per track with Core for 9 fields including the keyword tags, 2 with Ultra for all 35); balance checks and file search are free. Works with Cursor and Claude Code too (full walkthrough in the developer docs).

The Studio API is programmatic access to the same analysis engine that powers batches: send a track, get back up to 35 metadata fields (BPM, key, genres, subgenres, moods, emotions, instruments, vocal type, energy, danceability, a written description and a ready-to-paste tag list). It is built for platforms, tools and labels that want tagging inside their own pipeline: a beat marketplace auto-tagging every upload, a label enriching a delivery spreadsheet, a DJ app showing analysis in its own UI. Billing is the same credit balance you already use in Studio: 1 credit per track on Core, 2 on Ultra. Both run the same engine and are equally accurate; Core returns 9 fields including the keyword tag list, Ultra returns all 35. Full reference lives at tracktag.me/developers.

Head to Studio → API (left sidebar). Click Create key, give it a label ("Production", "Staging"), and copy the key immediately: for security the full key is shown exactly once; we store only a fingerprint. • Live keys (tt_live_…) run real analyses and charge credits. • Test keys (tt_test_…) are free and return a truncated preview, perfect while you build. Lost a key? Use Roll: it issues a fresh key and revokes the old one in the same step. Revoke kills a key instantly. You can hold up to 5 live and 5 test keys, and the API tab shows each key's last-used time plus a 30-day usage summary: requests, analyses, failures (auto-refunded) and credits spent.

You never upload tracks into a TrackTag library. Your system sends POST /v1/analyze with either an audio_url (any https link: your CDN, an S3 signed URL, up to 60 MB) or the file inline as base64 (up to 15 MB). We download the audio, analyze it, return the metadata and discard the file. Nothing is stored except the results. The call returns a job id immediately; analysis typically takes 5–15 seconds. Get the result two ways: • Poll GET /v1/jobs/{id} until status is "done". • Or pass a webhook_url and we push the finished result to your server, signed so you can verify it came from us. For quick one-offs, add ?wait=true and the call simply returns the finished analysis in one round-trip.

curl -X POST https://aaeabanvqnndwgrqsmhg.supabase.co/functions/v1/api-v1/v1/analyze \
  -H "Authorization: Bearer tt_live_YOUR_KEY" -H "Content-Type: application/json" \
  -d '{"audio_url": "https://your-cdn.com/track.mp3", "model": "core"}'

API calls draw from your normal Studio balance: one pool, one ledger. Core = 1 credit per track (9 fields, keyword tags included), Ultra = 2 (all 35). Same engine and same accuracy on both. Every API charge appears in your Studio credit ledger tagged "api:", so you can always tell app usage from API usage. You only pay for delivered results: if a job fails for any reason (the audio could not be downloaded, the engine errored, the job timed out), its credits are refunded automatically within minutes, and the refund shows in the ledger too. Rate limits: 10 requests/minute and 2,000 analyses/day per key by default. Building something bigger? Contact us: higher limits are available for platforms and labels.

The avatar menu → My profile shows your account: name, email, plan and credit stats. The avatar itself is generated: press the shuffle in the profile card to roll a new look; your choice is remembered per account. The same menu holds "What's new", a running list of everything we have shipped, with a red dot when there is something you have not read yet. It is the fastest way to find out what changed since your last session. Below it, "Send feedback" reaches us directly, and the feature request board lets you post an idea and vote on everyone else's.

Settings collects everything configurable: • Batch naming: the pattern used to suggest batch names (date, folder, counter). • Sounds: completion chime and click feedback on/off. • Alerts: low-credit warnings and completion notifications. • Player: preview volume and behavior. • Tag formatting: case, prefix, suffix rules. • Custom taxonomy: your vocabulary mapping. • Library: auto-sync toggle, hidden folders, display density. • Unlimited-BYOK: API key connection for the flat-rate plan. Account-level data (presets, taxonomy, flags) syncs to your account; device-level cosmetics (density, layout) stay per machine.

Sign out from the avatar menu. In Studio you return to the Studio landing page; in the Lab you return to the Lab. On shared machines, accounts are fully isolated: when a different account signs in, all locally cached Studio data from the previous account (history cache, settings, any API key) is cleared automatically, and the new account loads its own data from the server.

Account deletion is available from the profile area and removes your profile, analysis library, presets and stored data from our systems, along with your sign-in identity. It closes both your Studio and your Lab account. Any credits still on the balance are forfeited and are not refunded, so spend them first if you want their value. Deletion is permanent. Export anything you want to keep before confirming.

Check the format first: Studio accepts MP3, WAV, AIFF, FLAC, M4A, OGG and AAC. Files with the right extension can still fail if the audio inside is corrupted or zero-length; those are flagged as failed (and not charged). Very large single files (multi-hour DJ sets) can time out. Split them or analyze the radio edit. If drag-and-drop misbehaves in the browser, use the click-to-browse picker instead.

Give a slow track a minute. Long files take longer. If the run is truly frozen: check your internet connection, then press Stop (finished tracks are kept and charged, the rest are not) and re-queue the remainder. If a specific file fails repeatedly, it is almost always the file. Try re-exporting it from your DAW. Still stuck? Contact support with the batch name and the approximate time. We can see failed runs on our side.

In browsers, Chrome/Edge/Brave forget folder permissions after a restart. Click Reconnect and confirm the picker; your index and tags are untouched. Firefox and Safari do not support folder connections at all (browser limitation). Use Chrome-family browsers or the desktop app. In the desktop app folders should never disconnect. If a folder scan comes back empty on a Mac, check System Settings → Privacy & Security → Files and Folders and make sure TrackTag Studio has access.

Mac: the app is notarized by Apple, so a plain "unidentified developer" block should not appear. If macOS complains, make sure the DMG finished downloading fully and reopen it. Windows: SmartScreen shows "Windows protected your PC" on new releases: click "More info", then "Run anyway". This is Microsoft's reputation system warming up to a new installer, not a problem with the file.

Credits land the moment Stripe confirms payment. A refresh usually reveals them. If the balance still looks wrong, check the Stripe receipt email and contact support with it; we can trace every purchase and fix the balance on our side.

Every page carries a live status dot in the footer. Green means every part of TrackTag is answering normally; if anything is degraded or down, the dot changes colour and says so. It is checked independently of the app, so it stays honest even when something is broken. Click it (or go to status.tracktag.me) for the full picture: the website, the analysis engine, the public API and sign-in are each monitored separately, from outside our infrastructure, around the clock. The page also shows recent incidents and past uptime, and you can subscribe there to be notified when something changes. So when a batch will not start, check the status page first. If everything is green the problem is local (connection, file, browser) and the articles above will get you further; if something is red, we already know and are on it.

The support page reaches a human, typically within 24 hours. Pick the closest subject (account, billing, bug, Studio, general), tell us what happened and what you expected, and include file or batch names when relevant. Feature requests are welcome through the same form; a lot of Studio exists because someone asked.