Quick answer
If the new file is a revised version of the same document, replacing the file that is already there is usually safer than deleting it and uploading a new one.
If the new file is a separate publication that should sit alongside the old one, upload it as a new item.
That is an editorial decision about what the document is, not a decision about which button is easier to click.
The question to ask
Does this page still mean the same thing?
If it does, replace the file.
If it does not, the new file deserves its own place on the site.
Some examples
| What arrived | Replace | Publish as new |
|---|---|---|
| Current employee handbook | ✓ | |
| Corrected application form | ✓ | |
| Current product manual | ✓ | |
| Annual Report 2026 | ✓ | |
| September board minutes | ✓ | |
| New catalog edition, old one kept | ✓ | |
| Typo fixed in the current guide | ✓ |
That table is not a WordPress rule. It is a publishing decision, and you are the only one who can make it.
Why deleting and re-uploading causes problems
Deleting the old item removes the exact thing your pages are pointing at.
Uploading the replacement as a new item usually gives you:
- a new entry in the Media Library
- a different uploads folder
-1on the end of the filename- pages still linking to the file you deleted
- two copies of the same document.
You then have to go and update every reference by hand, and find the ones you did not know about.
Why replacing is usually cleaner
If the file that is already there has the right page relationships, a URL people have bookmarked, a custom field pointing at it, external links, and a position in search results, then keeping all of that and changing only the file is far less work — and far less risk.
When replacing is the wrong answer
Replacing is dangerous when the old version matters.
Annual reports. The 2026 report should not overwrite 2025 if both belong in the archive.
Board minutes. October’s minutes are not a corrected version of September’s.
Product revisions. Someone still running the old model may need Revision B long after Revision C ships.
How the file is referenced matters
Some pages link to a file by its address. Some store a reference to the Media Library entry. Some plugins store something of their own.
That changes what deleting actually breaks. A replacement workflow has to work the way the reference is really stored, rather than assuming everything is a URL.
Files used on several pages
Say one PDF is linked from five pages.
Replacing it updates all five, which is usually what you want for a “current version” document.
Deleting it and uploading a new one leaves all five pointing at something that no longer exists.
What happens to the cache
Replacing a file keeps the URL, which is the point.
It also means anything caching that URL will happily keep serving the old version. After replacing, check the file itself, your CDN, your browser, and — if the reference changed rather than the file — the page HTML.
Example: updating the employee handbook
The HR page links to employee-handbook.pdf, and so does every onboarding email you have ever sent.
A revised handbook is approved.
The right move: keep the file in place, replace it, open the public link and check it, purge the cache if it is stale, and archive the old version separately if your records policy needs it.
Deleting and re-uploading breaks every one of those emails for no reason.
Example: the annual report archive
The site lists the 2024 and 2025 annual reports. The 2026 report arrives.
The right move: publish 2026 as a new item, leave 2024 and 2025 exactly as they are, and replace nothing.
A real folder needs both
An incoming folder often has 80 revisions and 10 genuinely new documents in it.
A batch tool has to handle both in the same run — replace the ones that have a home, add the ones that do not — rather than forcing everything through one or the other.
Mistakes worth avoiding
Deleting before you have checked what uses it. The old file may be referenced by content you have not found yet, and deleting first removes the thing you would have used to find it.
Uploading the new one and forgetting the old links. The new file looks perfect in the Media Library while visitors carry on downloading the old one.
Treating an archive like a current document. One convenient replacement can quietly erase a year of history.
Assuming everything is a URL. Custom fields and stored references do not behave the same way.
One sentence that prevents most of this
Before you touch anything, finish this sentence:
This page is ________.
If the answer is “the current version of X”, replace the file.
If the answer is “the 2025 edition of X”, publish a new one.
That single sentence catches nearly every version of this mistake.
Summary
Replace when it is still the same current document.
Publish as new when it is a new edition or a record of something.
Do not let the way WordPress happens to handle uploads make that decision for you.
Related: Replace PDF without breaking links · Annual reports · Media Library bulk replacement