The filenames of created backups are a bit different:

• For the snapshot backups there’s a filename.ext@yyyy-mm-dd_hhmmss file created (not literally, of course, hopefully that is understood).

• For the backup-on-save you get either filename.ext.bak (for Simple backup) or filename.ext.yyyy-mm-dd_hhmmss.bak (for Verbose backup).

Yes, I think it does, thanks! So it’s OK to keep the same directory for both, since one is for the backups of the opened files, and the other is for the session of the files that are open (just to confirm).

If you have session snapshot and periodic backup enabled it means
that the files, currently loaded, are saved in the configured “backup” directory.
Those aren’t real backups. Let me try to explain with an example:

• user opens file X and modifies it
• npp is creating a “backup” file with the current content

the user has now the real file on disk and an additional “backup” file
create in a different location. But this “backup” file has a different
content then the original file.
User does further changes to the current loaded file
but still does not save it then only the “backup” file does get modified.
Once the user hits save, the real file gets updated and the “backup” file gets deleted. So the theory. But sometimes shit happens.
The backup on save feature creates a real backup - two files with identical content.

Does this makes sense to you?

Do you know what the difference is between “session backup” and “backup on save” is? Would you suggest having a “Backup” folder within my NPP cloud folder, and point both directories to that same one (or need they be different)?

I don’t use this myself but there is an setting Cloud which can be used for this.
And I assume you have to modify your backup path.