Browse help topics
Document Library

Replace a document without changing its links

Upload a new version of a document while keeping its existing Share Links, Room placements, access settings, and recipient URLs.

Updated October 11, 2026

Examples use sample data. Available controls may vary by plan, role, and product version.

Use Replace when the file changed but the sharing setup should not. HummingDeck keeps the document record, existing Share Links, Room placements, recipients, and access settings. People opening those URLs see the new version, so you do not need to send another link.

Product exampleBased on the live Replace Document dialog

Replace Document

Upload a new version of this document.

This permanently replaces the current document. All existing links will point to the new version.

Drop a PDF here or choose a file

The replacement must match the original file type.

Replace the document

  1. Open Document Library and select the document.
  2. Select Replace in the document header.
  3. Choose the new file from your device.
  4. Confirm Replace Document.
  5. Wait for processing to finish, then check the preview or test the download-only file before relying on the live links.

The new file must be the same type as the original. For example, replace a PDF with a PDF. If you need to change file type, upload a separate document and create the appropriate sharing setup for it.

For Excel workbooks, replace .xlsx with .xlsx and .xls with .xls.

The delivery mode also stays the same. A download-only PDF must be replaced with a PDF, and a download-only ZIP with a ZIP; both remain download-only. To switch between browser preview and download-only, upload a separate document. If the replacement needs encryption, encrypt it before upload and give recipients any new password separately.

To use a revision from Google Slides, Google Docs, or another online editor, first download or export it in the same supported format, then select the local file. Document replacement does not accept remote links.

Plan: All plans

Replace from an integration

Workspaces with API access can replace a document using POST /decks/{deckId}/replace. Send a local file in the multipart file field with a manually issued workspace API key that has documents:write. Zapier OAuth cannot use this operation. The API accepts a file up to 30 MiB and a complete multipart request up to 31 MiB. The response reports pending while a previewable file is processing, or completed for a download-only PDF or ZIP. Check the new file before relying on the live links. A repeated POST starts a new replacement. If the response is lost, inspect the current document or share view, or contact support before retrying. See the API reference for request and error details.

Use a filename extension that matches the file type, such as .pdf, .pptx, or .docx. Missing or mismatched extensions return INVALID_FORMAT.

What stays the same

Replacing the file keeps:

  • existing document and Room links;
  • recipient and company associations;
  • open, email-gated, or Restricted Access settings;
  • download, expiration, and notification settings;
  • browser-preview or download-only delivery mode;
  • the document’s existing activity and analytics history.

The Library title also stays the same unless you edit it separately. A copy that someone downloaded before the replacement does not update on their device.

What changes

Opening or reloading any active link or Room placement after processing loads the new version. For HTML files and HTML bundles, recipients who open the link during processing see a preparation screen. The document opens automatically when it is ready. If the link shows a processing error, replace the file and wait for processing to finish.

A viewer that stayed open during replacement must be reloaded. For an HTML bundle, check the updated pages, images, styles, and links in the same browser you used before replacement.

Replacing a document is useful for:

  • revised pricing or commercial terms;
  • corrected pitch decks and reports;
  • updated implementation or onboarding plans;
  • refreshed event, training, or partner material;
  • a new export from Google Slides, Google Docs, Canva, or another authoring tool.

For a Room example, watch Update a client portal's document without changing its link. The tutorial uses Replace for a new version while keeping the existing portal link and activity history.

Protect the meaning of historical analytics

Existing sessions remain part of the document history. If page count, order, or meaning changes, an older “page 7” event may refer to different content than page 7 in the replacement.

For small corrections, keeping the same document is usually clearer. For a major restructure or a new reporting period, a separate document can preserve cleaner version-specific analytics.

Replace is unavailable while the document has an active Proposal link with recipient response controls. This prevents the terms from changing underneath an active decision flow.

If the proposal should no longer remain active, revoke the appropriate Proposal link before replacing the document. If the earlier proposal must remain available as sent, upload the revision as a separate document instead.

Tell recipients about material changes

The same URL is convenient, but it should not make an important change invisible. Tell recipients when you replace pricing, legal terms, scope, deadlines, or another decision point they may already have reviewed.

For other link changes, see Manage share links and recipient controls. If the new version does not process, see Troubleshoot uploads and processing.