Built for independent producers · 0% platform commission on every plan · Start free

Help center

Wiki & FAQ

Step-by-step guides for payments, domains, storefront setup, products, and troubleshooting.

Back to Help Center

Uploading beats

Upload error codes

What each upload error code (UP-101, UP-301…) means, and how to fix the upload.

When an upload fails, Trakroom shows a short code such as "Error UP-301" at the end of the message. Find the code below to see what happened and how to fix it. If a fix doesn't work, send the code to Trakroom support — it matches what the support team sees.

The file or request:

  • UP-101 — Signed out. The upload request had no valid session — the producer was signed out in another tab, or the session expired during a long upload. What to do: Sign in again, then retry the upload.
  • UP-102 — Upload request was incomplete. The browser sent an upload request without a file name, type or valid path. Almost always an outdated page after a Trakroom update. What to do: Refresh the page and try again.
  • UP-103 — Wrong file type for this slot. The file's type doesn't match the slot it was dropped on — for example a ZIP in the artwork slot, or a WAV in the tagged MP3 slot. What to do: Drop the file on its matching slot: artwork images, MP3s, WAV masters and stems ZIPs each have their own.
  • UP-104 — Image over 3 MB. Artwork and site images are capped at 3 MB. The browser normally shrinks larger images first, so this means that step failed or was skipped. What to do: Export the image as a JPEG or WebP under 3 MB and upload it again.
  • UP-105 — File size unknown. The browser didn't report the file's size, which Trakroom needs before accepting beat audio or stems. What to do: Re-select the file from your computer (not a cloud drive shortcut), or try another browser.
  • UP-106 — File over Trakroom's limit for this slot. The file is larger than the platform maximum for that kind of beat file. This is separate from plan limits. What to do: Export a smaller file — a lower sample rate for WAVs, or a leaner stems archive.
  • UP-107 — Product not found. The upload targeted a product that doesn't exist, belongs to another store, or was deleted. What to do: Reload the product and try again. If it was deleted, create a new one.
  • UP-108 — File isn't in your store's library. The file referenced isn't in this store's storage folder — usually a stale page after switching stores or accounts. What to do: Refresh the page and upload the file again.

Plan limits:

  • UP-201 — Stems need a paid plan. ZIP/RAR stems uploads require the Starter plan or higher. What to do: Upgrade your plan to upload stems, or sell the beat without them.
  • UP-202 — File over your plan's size limit. A single file is larger than the plan's maximum upload size. What to do: Upgrade your plan, or export a smaller file.
  • UP-203 — Storage limit reached. This upload would take the store past its storage limit. What to do: Delete files you no longer need in the Media Library, or upgrade your plan for more storage.
  • UP-204 — Voice tagging needs a paid plan. Generating a tagged preview requires a plan that includes Auto voicetag. What to do: Upgrade to Starter or higher, or upload your own tagged MP3 in the preview slot.
  • UP-205 — Bulk upload is turned off. Media Library bulk upload is disabled for this store, either by its plan or by a per-store override set by Trakroom staff. What to do: Upload files from the product editor instead, or contact Trakroom support if you think this is a mistake.
  • UP-206 — Too many uploads at once. The store requested more Media Library upload links in the last hour than the bulk-upload limit allows. What to do: Wait a little while, then upload the remaining files.

Sending the file:

  • UP-301 — Connection lost during upload. The browser couldn't reach storage, or the connection dropped mid-transfer. Common causes: unstable Wi-Fi or mobile data, a VPN or ad blocker, or the computer going to sleep. What to do: Check your connection, pause any VPN or blocker, and retry. Large WAVs and stems upload best on a stable connection.
  • UP-302 — Storage rejected the file. Storage refused the transfer; the HTTP status is recorded. Often a browser extension altering the request, or the file changing on disk while it uploaded. What to do: Retry the upload. If it keeps happening, try another browser.
  • UP-303 — Upload link expired. Each file gets a one-time upload link valid for 10 minutes. The transfer didn't start in time — typically a slow connection with several large files queued. What to do: Retry the upload; a fresh link is made each time. Upload large files one at a time.
  • UP-304 — Couldn't reach Trakroom. The browser couldn't contact Trakroom to start or finish the upload — offline, or blocked by a network filter. What to do: Check your internet connection and try again.

After the file arrived:

  • UP-401 — Upload couldn't be confirmed. The file was sent, but Trakroom couldn't find or read it in storage afterwards. What to do: Upload the file again.
  • UP-402 — MP3 conversion failed. Trakroom couldn't create the MP3 from the uploaded WAV or lossless file — usually a corrupt, unusual or very long audio file. The recorded detail shows the encoder's reason. What to do: Re-export the WAV as 16- or 24-bit PCM and upload it again, or upload your own MP3.
  • UP-403 — Tagged preview couldn't be created. Mixing the voice tag over the beat failed. The recorded detail shows why. What to do: Try again. If it repeats, upload your own tagged MP3 in the preview slot and contact support with this code.
  • UP-404 — Audio file missing from storage. The track's master, or a voice tag's audio, no longer exists in storage. What to do: Re-upload the master (or the voice tag, in your tag library) and try again.

Trakroom's side:

  • UP-501 — Storage unavailable. Trakroom couldn't create an upload link — a storage configuration problem or an outage on Trakroom's side. What to do: Try again in a few minutes. If it persists, contact support with this code.
  • UP-599 — Unexpected upload error. An error with no specific code. The recorded detail has the underlying message. What to do: Try again, and contact support with this code if it keeps happening.