---
title: Upload or replace a digital product file
description: "How to upload a new digital product file or replace an existing one on Tapmy without breaking delivery for buyers who already purchased."
lead:
  - "To replace a digital product file on Tapmy, back up the current version, test the new file on a clean device, swap it in the right offer, then run a signed-out delivery test. Do not assume existing buyers are notified or receive the new file automatically."
tags:
  - digital-products
source: docs/tapmy-wiki/pages/upload-or-replace-a-digital-product-file--f88fb687.md
---

This guide is for creators publishing a new download or updating an existing one.

## What should I prepare before replacing a file? {#before-you-start}

Have the final file, a clean filename, short release notes and a backup of the live file. Think about who has already bought it, what support questions an update could cause, and whether the change alters what you promised.

Use original or properly licensed content. Keep a backup of every source file and note which version is live now.

## How do I replace a file safely? {#publish-a-controlled-file-version}

Treat a swap like a small release. The questions that matter: which offer points at the file, what existing buyers get, and whether old links or cached copies still work.

1. Download and archive the current live file. Note its filename, upload date and the offer it belongs to.
2. Test the new file on a clean device. Check it is complete and that links, fonts and media work. Scan for malware and make sure the buyer has the software needed to open it.
3. Name it clearly, with product and version. Strip personal metadata, internal comments and leftover draft assets.
4. Open the right product's delivery settings and choose the upload or replace option shown there.
5. Read any warning about existing orders, access, links or notifications. If the effect is unclear, stop and ask Support.
6. Save, then preview the offer. Make sure the sales page text and requirements still match.
7. Run a test as a buyer and confirm you get the new version, not a cached or old one.
8. If existing buyers should hear about it, use a notification method you have confirmed, say what changed, and do not expose your buyer list.

## What does success look like? {#what-success-looks-like}

The offer hands a clean buyer session the new, tested file. You can still recover the old version, and you know whether existing buyers keep or receive access. The sales page and release notes match the new file.

Check it signed out and, if access is involved, with a test buyer. A published sales page does not prove delivery works.

## Common problems {#troubleshooting-and-limits}

- **The upload fails.** Check format and size, the filename, whether the file is corrupt and your connection. Try a smaller file that you know works.
- **The old file still downloads.** Look at which asset is attached, the publish state, cache and the access link before you upload another copy.
- **Existing buyers lost access.** Keep the order evidence, compare how access should behave, restore the last good file if it is safe, and contact Support.

Tapmy does not document exact replacement behavior, automatic buyer notices, file retention, link expiry, version history or a download size limit, so test rather than assume. Keep the previous file until you know you can roll back.

If a buyer may have paid, do not repeat a charge, delete the order or remove access while you investigate. Capture redacted order, buyer, product and timestamp details first.

## What next? {#next-steps}

Update the sales page if the format, contents, requirements or license changed, then watch access and support requests after release.

If it still fails, [contact Tapmy Support](/help/tapmy-support) with the public offer URL, the buyer email used at checkout, an order or receipt reference if you have one, the exact time and time zone, what you expected and redacted screenshots. Never send passwords, codes, full card data, private keys or customers' copyrighted content.