Undo/Redo Revisions History

A history of all the revisions made under one backup, where you can see and restore every single change you made to a specific page (e.g. first revision = "added tag for Heading 1 in 'hero section', second revision = "changed color of 'paragraph-big' to green," etc.). This is more convenient than clicking the undo button a bunch of times.

  • Josiah Kniep
  • Feb 19 2017
  • Brennin Wall commented
    18 Sep, 2023 09:33pm

    Restore from the last published at the very least

  • Kim commented
    6 Dec, 2021 04:28pm

    Yesss this would be very handy right now

  • Maarten Lodewijk Anne Veldhuijzen commented
    27 Dec, 2020 02:55pm

    Critical. Now writing everything by hand. Ridiculous.

  • Mark Savage commented
    18 Mar, 2019 04:44pm

    This is essential. As it stands I can't see what changes I'm undo-ing or re-doing, and have no idea of the length of undo history.

  • Cameron Roe commented
    20 Oct, 2018 11:18pm

    See also: https://wishlist.webflow.com/ideas/WEBFLOW-I-1517

  • Robert Cat commented
    5 Oct, 2018 12:43am

    Must Have

  • Tom Lamers commented
    12 Apr, 2018 12:19pm

    I second this (photoshop way)

  • Kristine Paulsen commented
    30 Mar, 2018 06:01pm

    Yes please! I wouldn't necessarily need a giant list, but maybe the last 20 or so changes would be great to be able to see and access. (Think: what Photoshop can do.) 

  • Shahab commented
    27 Jul, 2017 08:30am

    This would be very useful.

    It's very easy to get lost with the current method when clicking undo a few time. Seeing a list of changes that you could go back to would make this easier. I understand the list can get very long over time but just showing the last 10 or so changes would suffice

  • Studio2bDesigns .com commented
    2 Mar, 2017 12:54pm

    Personally I think the list of changes in-between backups could easily become quite lengthy and difficult to manage.. However I do think it's a great idea.. Perhaps the ability to simply add "Notes" yourself manually for each backup would be somewhat effective as well? Much easier to implement as well.

  • +26