As Content Editor, why can't I "Replace Attachment" on a Button that opens a PDF file?

I have several new Content Editors and I need them to replace the PDF files that open when buttons are pressed. See attached images.

While testing this out I realized that even though he has Publish capabilities, Webflow’s “Replace Attachment” functionality within the cog of a Button does not seem to work at all when in Editor mode. It only works in Designer mode. He can see the files that he wants to use, but he cannot actually select one and see it reflect in the Button settings.

I can see this written as functionality available to Content Editors (and they have Publish Access) in the docs.

Thanks for any help you can provide.



Here is my site Read-Only: LINK
(how to share your site Read-Only link)

Yep, it’s just not supported.
You’d have to ask Webflow support as to the “why”.

Some options;

  • Try using the CMS for the PDF storage, and connect your button to that PDF record for download
  • Store the PDFs externally… dropbox or Google Drive, and have the user update the link to them

Thank you for the response, @memetican! I may need to try out that alternate CMS option to see how streamlined it could be for them.

For Webflow Support, I would be curious as to why this isn’t supported and why there is no error handling. Very confusing and not an ideal user experience to make it appear functional.

We just encountered a similar problem, content Editors cannot choose the ‘link a PDF’ option on the button. How can this be such a problem to implement? For many big organisations it makes no sense that content editors don’t have access to upload a PDF on a button.

Hey @_vOn,

The legacy editor has never support access to the assets panel in any form, which is why you cannot upload a PDF, or even get the URL to link to an existing one.

This is one of many big reasons for the migration to Designer edit mode [ yay! ], where this will be possible.

By the way, I suspect you could give your client access now if you needed to- but-

  • until the editor-seat migration happens mid-2025 you’d need to purchase a “limited” seat for each editor.
  • “limited” seats are are workspace-wide so you’d have to figure out how to lock down access to their single site.