How do you link slides across presentations so they update?

To link slides across presentations is to hold one slide as the single source and give every deck that uses it a connection back to that source, so one edit reaches every copy in circulation. PowerPoint has no feature that does this. A slide pasted into a second deck becomes an independent copy, and the original keeps no record that the copy exists.

The question comes up in teams that reuse the same disclaimer, pricing, company-overview or case study slide across dozens of client decks. This page covers what a slide link is, which native Microsoft 365 options come closest, what happened to the two Microsoft features that came closest to linking slides across presentations, and how slide libraries provide the link instead.

What does it mean to link slides across presentations?

To link slides across presentations is to create a one-to-many relationship between a source slide held in a central library and every instance of that slide placed in a working deck. The instance stores a pointer back to the source and the version of the source at the moment it was inserted. When the source changes, every instance can report that it is out of date.

Two states define the model. The source slide, also called the root slide, is the authoritative version, owned by one named person and edited in one place. The linked instance is the copy sitting in a working deck, carrying the pointer and the version stamp that make the link readable.

A copy-pasted slide carries neither. Copy and paste moves the shapes, the text and the formatting into the destination deck and ends the relationship there. Nobody can then answer which decks hold the slide, which version each one holds, or who needs to be told when the figure on it changes.

The distinction matters most at the moment a number changes. A pricing slide corrected in the master deck is corrected in one file. Every client deck already holding a copy of it stays wrong until somebody opens that deck and fixes the slide by hand.

Can PowerPoint link slides across presentations?

PowerPoint cannot link slides across presentations. No release of PowerPoint on Windows, Mac or the web provides a slide-level link that binds a slide in one deck to a source slide in another and refreshes it when the source is edited. Microsoft's own guidance for reusing slide content is to copy and paste slides between presentations or duplicate an existing presentation.

Five native mechanisms come close enough that teams try them, and each one solves a narrower problem than the question implies. The table below names what each mechanism does and where it stops.

Every row is a real Microsoft 365 capability doing the job it was designed for. None of them answers the question that brings people here, which is how one approved slide stays current in thirty decks owned by twenty people.

What happened to the SharePoint Slide Library and Reuse Slides?

Microsoft has retired both features that came closest to linking slides across presentations. SharePoint Server 2007 and 2010 offered Slide Libraries, which published individual slides and prompted PowerPoint to notify a user when a published slide had changed. Slide Libraries were deprecated from SharePoint 2013 onward and were never available in SharePoint Online.

The second retirement is current. Microsoft message centre post MC1179161 announced that the Reuse Slides feature in PowerPoint retires starting January 2026 on Windows and Mac desktop, removed from the ribbon with no option to re-enable it. The stated reason is interface simplification and duplication with existing copy and reuse workflows, and the stated alternative is copying and pasting slides or duplicating a presentation.

The first retirement is the one that matters to the linking question. A SharePoint Slide Library was the only native mechanism that ever told a user a slide in their deck was out of date. That notification is the piece teams describe when they search for a way to link slides across presentations, and it now sits in third-party slide library software delivered as a Microsoft 365 add-in. Microsoft 365 itself no longer carries it.

How does linked-slide propagation work?

Linked-slide propagation is the mechanism that links slides across presentations in practice, and it works in four steps. A content owner edits and republishes the source slide. Every linked instance registers a version mismatch. The user who opens a deck holding that instance sees an update notification inside PowerPoint. The user accepts the change per slide or across the whole deck, and the platform writes each accepted update to an audit trail.

The notification travels through the Microsoft 365 add-in and arrives when the deck is opened in PowerPoint. Decks sitting closed in SharePoint or OneDrive are not rewritten where they lie. The update lands the next time somebody opens the file, which is also the last moment before the deck gets used, and the point at which an old figure would otherwise reach a customer.

Acceptance is deliberate. Nothing changes inside a deck without the person holding it seeing what changed, and a rep who has tailored the surrounding slides decides per slide. Slides carrying approved language can be locked so the governed part updates while the editable placeholders around it stay as the rep left them.

Propagation logic, approval states and the comparison with file-level version history are covered in depth on the page about slide-level version control. The mechanics of storing, tagging and searching the source slides sit in the wider slide library category guide.

What are the options for keeping one slide current across many presentations?

Four approaches keep a slide current across many presentations, and they differ in what the link connects. The table below names representative tools for each approach and the situation each one suits.

A slide library with linked copies is the only approach that links slides across presentations at the level of the slide itself. It also carries the cost the other three avoid, which is governance. Somebody has to own each source slide and decide what happens when it changes. The evaluation around that trade sits on the build versus buy comparison.

Which slides are worth linking across presentations?

Listed below are 6 slide types that earn a link in most libraries. The qualifying test is reuse multiplied by change: a slide that appears in many decks and changes on a schedule.

• Disclaimer and regulatory slides: Approved language that has to read identically everywhere and that legal rewrites on its own cycle, which makes an untracked copy the highest-cost slide in the estate.
• Pricing and commercial terms: List prices, discount bands and packaging change by quarter, and an old price on a client deck starts a commercial conversation the account team has to unwind.
• Company overview and credentials: Headcount, office count, certifications and founding facts drift quietly, because no single person notices the day they stop being true.
• Case studies and client references: Reference permissions expire, results get restated and logos come off the approved list, and each of those changes has to reach every proposal already carrying the slide.
• Product and capability slides: Feature sets and positioning move faster than the decks describing them, and a deprecated capability on a live pitch deck sets an expectation somebody has to unwind.
• Data slides bound to a worksheet: Charts and tables tied to a company workbook through a link between Excel and PowerPoint, where the figure updates from the source and the slide around it stays approved.

Slides below the reuse-and-change bar stay ordinary copies. A library that links slides across presentations indiscriminately produces more update notifications than anyone reads, and unread notifications stop being read at all. Most libraries start with a few dozen source slides drawn from the highest-reuse content and grow the set as the team gets comfortable with the workflow.

What do you decide before linking slides across presentations?

Four decisions come before the first link. Each one is an ownership question, and the answers determine whether the links survive six months of daily use.

1. Who owns each source slide: Name one person accountable for the content of each source slide. An unowned source slide ages the same way an unowned file does, and the link then propagates a stale claim faster than copy and paste would have.
2. What is locked and what is open: Decide, per slide, which elements carry approved content and stay locked, and which are placeholders a rep fills with the client name, the figures and the local detail. That split is what lets a linked slide survive tailoring.
3. How existing copies become linked instances: Decide whether the decks already in circulation get linked to the new source slides or left alone as a legacy set. Linking the live decks is what makes the first propagation visible to the people whose habits have to change.
4. How often the source gets reviewed: Set a review cadence for the source slides themselves, so the number on the credentials slide is checked on a schedule rather than when somebody spots it in a meeting. The content audit method covers what that review reads.

Teams that skip the ownership decision get the most common failure in the category. The links work, the propagation works, and nobody edits the source, so the library becomes an accurate record of what was true at launch.

How does SlideHub link slides across presentations?

SlideHub links slides across presentations by holding each approved slide as a separately governed item with its own owner, metadata and version history, and by inserting it into working decks as a linked instance rather than a loose copy. Reps search the library from a pane inside PowerPoint, insert the slide they need, and keep building. The link travels with the slide.

When the owner edits and republishes a source slide, every deck holding a linked instance is marked out of date. The next person to open that deck in PowerPoint sees which slides changed and accepts the update per slide or across the deck. Content owners see which documents still carry a superseded copy, which is the question that has no answer at all in a folder of PowerPoint files. The update side of the platform and slide-level version history cover the mechanics in product terms.

Locked elements and open placeholders are what keep the link intact through real use. A rep tailors the client name, the numbers and the local detail without touching the approved part, so the deck stays personal and the next source-slide update still lands cleanly on it. Charts bound through Excel Link take the same route for data: the figure follows the company worksheet, and nobody opens a slide to correct a number.

More than 500 organizations and over 10,000 professionals use SlideHub each month, including KPMG, Thyssenkrupp, Netcompany and Bech-Bruun, and the platform holds 4.9 stars on G2. SlideHub is SOC 2 Type II and Cyber Essentials certified, is a Microsoft 365 certified application, and hosts customer data in the EU (AWS Ireland) under GDPR, with audit logging across content and administrative events. Procurement detail sits on the security overview. Teams planning a source-slide programme can compare plans on the pricing page or book a 30-minute walkthrough and bring the slide that already lives in every deck the team ships.

Frequently asked questions about linking slides across presentations

Can you link a slide from one PowerPoint presentation to another?

Not in PowerPoint. PowerPoint offers no slide-level link that binds a slide in one deck to a source slide in another and refreshes it when the source is edited. A slide moved between decks by copy and paste becomes an independent copy. Slide libraries delivered as Microsoft 365 add-ins add the link that PowerPoint does not provide.

Does a slide copied from another presentation update when the original changes?

No. Copy and paste moves the shapes, text and formatting into the destination deck and ends the relationship there. The original file keeps no record that the copy exists, and the copy keeps no pointer back to the original, so an edit to one never reaches the other.

What replaced the SharePoint Slide Library?

Third-party slide library software running as a Microsoft 365 add-in. SharePoint Server 2007 and 2010 offered Slide Libraries, which published individual slides and prompted PowerPoint when a published slide changed. Slide Libraries were deprecated from SharePoint 2013 onward and were never available in SharePoint Online, and Microsoft has published no native successor.

How do you update the same slide in multiple presentations?

Hold the slide once as a source slide owned by a named person, and insert it into working decks as linked instances rather than copies. Editing and republishing the source marks every instance out of date. Each user sees the change inside PowerPoint when they next open the deck and accepts it per slide or across the deck.