Publish a free PDF download in WordPress and keep its links reliable

Decide whether the document should be public

A free checklist, public report or printable worksheet may be suitable for an ordinary media upload. A customer invoice, private draft or paid ebook needs a different access and delivery design.

A hidden menu link is not file protection. A password on an article also does not establish that every linked upload is protected; WordPress’s post-password documentation describes controls with a narrower scope. Inspect actual file access when privacy matters.

For this workflow, assume anyone with the public file address can retrieve and share it unless your storage is separately restricted. Do not place private material in the Media Library and rely on an obscure filename as authorization.

Decide what visitors receive: the complete resource, its intended use and whether it is a current edition. A short landing page can explain that more clearly than a bare filename in a menu.

Prepare the PDF before uploading

Use a descriptive filename and check the document itself: title, edition or date where relevant, working links and correct page content. Remove material that should not be public, including accidental comments or personal information, using the source application’s supported review process.

Keep an editable source copy and an identifiable final PDF. A fictional maintenance checklist could have a landing page called Website launch checklist and a file named website-launch-checklist-2026.pdf. That example distinguishes the resource’s stable introduction from a particular edition.

Check the document’s size before publication. A long image-heavy file can be inconvenient on mobile data. Optimize through the document’s supported export tools while confirming that text, diagrams and links remain usable; a smaller file is not an improvement if essential detail becomes unreadable.

Add the native File block

Open the intended page or post, insert a File block through the block inserter or /file, then upload the document or select it from the Media Library. WordPress documents the controls in its File block guide.

Edit the visible file-link wording to describe the resource. “Website launch checklist — PDF” is clearer than “Click here.” Where useful, state the file size and edition in the surrounding text, using the actual values rather than an assumed template.

For a direct download route, select the media file rather than a separate attachment page as the destination. Decide whether to show the Download button and whether the ordinary link opens a new tab. Save the page and inspect the public result.

If upload fails, read the actual error and check the accepted file type, configured size limit and account permissions. The Media Add New guide explains the upload screen. Do not disable upload restrictions broadly or rename an unrelated file type to .pdf to force it through.

Keep a direct link even when embedding a preview

The File block can show an inline PDF embed and offers a display-height control. Use the embed when reading the document within the page is helpful, but keep a clear route to the file itself.

An embed is a presentation choice, not proof that every browser has the same PDF viewer. A visitor may prefer opening the file in another application, saving it or using the document outside the page.

For the fictional checklist, a concise HTML introduction, a direct PDF link and an optional preview can work together. Do not make the only download route a tiny control inside an embedded viewer. Check that the surrounding article remains usable if the preview is unavailable.

Expect download handling to vary on phones

A button labelled Download does not give the site complete control over a browser’s file handling. Mozilla documents that the HTML download attribute depends on factors including origin, browser and user settings; the file may be saved, prompt the user or open in a viewer. See the anchor-element reference.

A PDF opening on a phone is therefore not automatically evidence that the link is broken. Check whether the correct document opens and whether the device offers its usual save or share route. Avoid promising a particular folder or exact sequence of taps across all mobile platforms.

Server response headers can also influence presentation and filename. Mozilla’s Content-Disposition guide describes inline and attachment handling. Ask the responsible host or developer to inspect a problem rather than changing server headers blindly.

Review the PDF’s accessibility separately

Embedding a PDF does not automatically make the document accessible. Check its reading order, meaningful text, headings, links and any form fields using appropriate document tools and assistive-technology review.

WAI’s PDF reading-order technique explains checking logical reading and tab order. A two-column document can look correct while its underlying reading sequence is confusing.

Set an informative document title rather than relying only on the uploaded filename. WAI documents that in its PDF title technique. For informative images, review suitable text alternatives using WAI’s PDF image-alternative guidance.

Those are focused checks, not a complete accessibility certification. For a short checklist or essential instructions, providing equivalent useful HTML can also give readers a simpler route. An HTML summary that omits the important steps is not an equivalent replacement.

Choose an update strategy before sharing the link

Keep two addresses distinct: the page introducing the resource and the direct PDF URL. A stable introduction page can continue explaining the current edition while the file behind its link changes.

Uploading another file with the same local filename does not guarantee it overwrites the existing upload at the same URL. WordPress’s unique-filename routine can add a number to avoid a collision, and a different upload directory can also change the address.

The File block’s Replace control lets you select or upload another file for that block. Do not assume it updates every other link to the old PDF across articles, menus or external messages. Record the old and new file URLs and check all references you control.

If a contract or established distribution genuinely requires the exact direct URL to remain stable, use a supported replacement workflow, preserve the previous file and verify the final bytes and caches at that address. This is a separate operation from changing one block’s selection.

Versioned files are often clearer when old editions remain meaningful. For a corrected document that must replace an unsafe old version, plan removal or redirection appropriately rather than leaving a misleading file public. Do not delete an old upload before checking the links that still depend on it.