Quick answer
If a page, an email, a bookmark, a QR code, a printed handout or someone else’s website already points at a PDF on your site, uploading a new version as a fresh file usually creates a different URL — and leaves every one of those links pointing at the old document.
To keep them working, replace the file behind the existing document rather than uploading the new version as unrelated media.
That is the right move when the new PDF is still the same document. If it is a separate edition that should stay available on its own, publish it as a new item instead.
Why uploading a new copy breaks things
A normal WordPress upload is built to create new media, not to update something that already exists.
Depending on your site, that usually means:
- a new entry in the Media Library
- the file lands in this month’s uploads folder
- WordPress adds
-1to the filename to avoid a clash - your existing pages carry on linking to the old file
- you now have two copies and no obvious way to tell which is current.
That is sensible behavior for new content. It is just not the same thing as replacing something.
“Keep the same link” can mean several things
People use that phrase for at least five different things:
- the direct URL of the file itself
- the page that links to the file
- the entry WordPress keeps for that file
- a custom field pointing at it
- the QR code or emailed link someone else is holding.
They are related, but they are not the same. Before you replace anything, work out which of those actually has to stay put.
The direct file URL
Something like:
https://example.com/wp-content/uploads/2025/05/application.pdf
If that exact address is in an email or printed on a form, it is the thing that matters.
How WordPress stores the file
Some content links to the file by its address. Some stores a reference to the Media Library entry instead. If your pages do the latter, keeping that entry intact matters as much as keeping the path.
Custom fields
A custom field might hold a reference to the Media Library entry, a URL, a file path, or something a plugin made up. A replacement has to work the way that field actually stores things rather than assuming every file reference looks the same.
Replace, or publish as new?
Replace when
- the page means “the current version”
- links people already have should keep working
- the old version should not be public any more
- nothing else about the page changes.
For example: Current Membership Form, Employee Handbook, Current Product Manual, Latest Price List.
Publish as new when
- the old document should stay available
- the date or version number is part of what the document is
- this is a new publication rather than a correction.
For example: Annual Report 2026, Board Minutes — September 2026, Manual Revision D.
Check whether the file is used elsewhere
The same PDF is often linked from more than one page.
If every one of those pages should show the current version, replacing it is exactly right.
If one of them is an archive page that should keep the old version, you need to separate them first — otherwise a single replacement rewrites the archive too.
Example: a typo found after an email went out
An organization sends 10,000 emails linking straight to:
membership-application.pdf
Then someone spots a typo.
Uploading a corrected file as:
membership-application-1.pdf
does nothing for the 10,000 links already sent. Replacing the file at the original address does.
After that you still need to check the cache — see below.
Example: annual reports
A “Current Annual Report” link is a replacement.
An archive page listing 2024, 2025 and 2026 needs each year published separately.
The filenames will not tell you which of those you are looking at. You will.
If the old PDF is still showing
A stable URL is a cacheable URL, which is usually what you want until the day you change the file.
If the old version is still appearing:
- check the file on the server is actually the new one
- look at the response and cache headers
- purge that specific file from your CDN
- try a different browser or device.
Do not upload another copy to get around it. That leaves you with three files and the same cache.
One file, or a folder of them
For a single PDF, a dedicated single-file replacement tool is plenty.
For 75 or 150 revised PDFs the job changes shape: working out which file goes where, checking the uncertain ones, making sure you are not changing pages outside the job, keeping track of what has been done, and being able to undo one mistake. That is what WP Bulk Replace is for.
FAQ
Does replacing a PDF always keep the exact same URL?
Not always — it depends on how your site stores and serves that file. Check the specific page and link you care about rather than assuming every WordPress setup behaves the same way.
Should I delete the old PDF first?
Usually not, if you care about the links. Deleting first can remove the very thing your pages are pointing at.
Why does WordPress add -1 to the filename?
Because it is creating a new file rather than overwriting an existing one, and it will not silently clobber something already there.
Why do I still see the old PDF after replacing it?
Almost always your browser or your CDN still has the old copy. See the section above.
Is undo the same as a public archive of old versions?
No. Undo is there for when something goes wrong. An archive is a deliberate decision to keep old editions published, and you set that up on purpose.
Summary
To replace a PDF without breaking existing links: keep the existing file in place rather than uploading a new one, check whether anything else on the site uses it, replace it, open the exact public URL to confirm, and keep undo available.
If the new file is really a separate edition, publish it separately instead.
CTA: Need to do this for a whole folder? See WP Bulk Replace.
Related: Bulk replace PDFs · Replaced file still shows old version · Replace vs delete and re-upload