How auto-save works

PublishFi saves your project automatically as you work. There is no save button to click and no manual export step required to preserve your edits — changes are written to the server in the background while you stay focused on the edit.

When saving happens

PublishFi does not save after every single keystroke or action. Instead, it waits until you pause editing for a moment before triggering a save. This approach — known as debouncing — means that a rapid series of actions like deleting several words, moving clips, and adjusting a property is grouped into a single save rather than triggering separate writes each time.

In practice, a save happens roughly a second and a half after you stop making changes. If you continue editing, the timer resets and waits again.

Unsaved changes protection

PublishFi watches for situations where you might accidentally leave the editor before a save has completed:

• Closing or refreshing the browser tab — your browser displays a "Leave site?" confirmation dialog, giving you a chance to stay and wait for the save to finish.
• Navigating within the app — PublishFi displays its own Unsaved Changes dialog with the message "Your changes are still being saved. If you leave now, some changes may be lost." You can choose Stay on page to wait, or Leave to proceed without waiting.

Both warnings appear only when there are changes in progress. If your project is fully saved, navigating away happens without any interruption.

If you lose your connection

If your internet connection drops mid-edit, the save attempt will fail silently. PublishFi keeps track of the pending changes and will protect against navigation as long as those changes have not been written to the server. When your connection is restored, making any small change will trigger a new save attempt.

If you are unsure whether your latest edits were saved, refreshing the page after reconnecting will load the last successfully saved version of your project. Any changes made since that save would need to be redone.

Tip: At the end of a long editing session, give the editor a moment after your last action before closing the tab. This ensures the debounce window has passed and your final changes have been written to the server.