Can you confirm that the files have been removed from the local album? That is controlled by checking Preferences>Album>Synchronise output directory

jAlbum’s uploader reads the manifest file, in the album’s root directory on the server, to speed up uploading and deleting unused project files. If you delete files outside of jAlbum and/or use another uploader then old files could be left on the server.

How are you uploading the album and how are you using SyncBackFree.

It would probably help if you could provide a link to the album and details of at least one file that was on the server that should not have been.

1/ I use Jalbum to upload files, always did.
2/ Last month, I looked at a folder on the internet album, because I was looking for the url of a picture. That's when I discovered that some files were with both old and new name. (I used Filezilla for that)
3/ I started Synckbackfree to see if I could find other errors, and I did of course.
This program compares local and web, and tells what the differences are. (see picture). By default, it can delete all unknown files, but I can skip some of them (such as the manifest ; see picture).
Album : http://www.galinou.fr/album/
wrong folder : http://www.galinou.fr/album/faune/animaux%20sauvages/insectes/abeilles%20and%20co/Fourmis/slides/

BTW, I did not execute the delete function so you can have a look...

Actually, if a file isn't listed in the manifest, jAlbum assumes that some other app put it there, and it will leave it alone.

The tricky thing about the manifest file is that if you make any changes to the contents of the server outside of jAlbum - using another FTP client, or deleting or adding some files - jAlbum isn't aware of what you've done, and the normal sync mechanism is defeated. You need to start with one clean upload from within jAlbum, and then never use any other mechanism.

You can delete the manifest file manually, then have jAlbum upload again - it will take a bit longer (because it has to check the time stamps on each file, as a regular FTP client would), and it will create a new manifest file.

But if you do that, it will not delete any extra files on the server, because it won't know who put those files on there. One might be inclined to say, "Why doesn't it just delete any file that's not part of the current album?" It's because there may be other files on the server that are needed - there might be robots.txt files, .htaccess files, server password files, custom 403 and 404 error pages, and so on. jAlbum can't just assume that anything it doesn't recognize can be dumped.

It might be handy to have an option in the uploader that says, "Upload the current album. If you find any other files in the target directory on the server, delete them, whether they're listed in the manifest file or not." It would need to have a fairly forceful "ARE YOU SURE?" dialog, to avoid disasters.

You're making this far more complicated than it really is. Make a small test album on your PC. Upload it, using the jAlbum uploader. Now go back into the project and delete one image, and add another one. Make the album again and upload it again. You should see that files on the server that are no longer needed are deleted automatically. There is nothing else the user needs to do. The uploader will keep everything synchronized.

BTW, I tried your idea :

I copied the .jap file and one little folder to d:/tmp
generate
upload
rename a file
generate again
upload

and YES the old file is deleted.

This means there is a problem on my true album, right ? but... where is it ?