FreeFileSync Forum

If we compare FFS to Robocopy (as it has certain similarities: mirror, update etc although not bi-directional sync), then the size limit simply excludes any file above the specified size but has no effect on any folders etc. I think Beyond Compare is the same as well.
To me this appears to be a ...

Your have probabably thought about this a lot more than me but I would assume this is not an issue for mirror or update which are both unidirectional.
I can indeed see it is more complex when it is a bi-directional sync for example.
May be the filter options should change depending upon the update ...

Yes, works as designed: When file size or time span filters are set, folder items are excluded.

But this ignoring of folder when filters are applied only appears to effect empty folders.
So if I have a Max size filter set, and I have a bunch of empty folders but 1 has a small file in it, that ...

...But maybe the setting only applies to new content instead of existing content, explaining the mkv situation....

I thought about this but that does not really work in practise as if the file grows in size over time starting in size below the Max Size filter but ending up far larger than it ...

Perhaps one of the Dev's can definatively say how the filters are supposed to behave, and whether the current behaviour is by design. That would clear this confusion up.
Personally I would be suprised if the Max Size filter is working as they intended.
The Minimum Size filter does work as I would ...

So as I uderstand it you are suggesting that the Max Size filter actually sets the minimum file size that a file can be to be copied ("So a filter setting max size of 200M excludes everything up to 200MB"). If this is so the the UI is just nuts.
Also what does the Minimum File size filter do? Set ...

I am pretty sure your interpretation of the Max Filter size is not correct. I have been researching this issue for a bit (see thread https://freefilesync.org/forum/viewtopic.php?p=37483 for more details and why this appears to be a bug). Notice in the top/1st screen grab above that the 4th and 5th ...

OK I think this is a bug possibly to do with Max Size filter.

1st Screen shot is with a Max Size of 200 Mbytes set and the empty folder will not be copied for some reason. Ignore the other large files - this was about another strange issue to do with Max File Size filter.
Next Test.jpg

This ...

I think there is another bug with maximum file size filter.
It appears to stop empty folders being copied to the destination.
See here with 200Mbyte Max Size Limit. Without Max Size Filter:

I assumed that FFS would copy empty folders to the destination (when they do not exist at the desitnation) when doing an update/mirror but it does not appear to be doing this for me.
Is there anyway I can get it to do this?

Glad we got there - thanks!
Do you take it from here e.g. report it?
I am new at this site so I am not sure of the procedure.

I think I might have a clue as to why you are not seeing my problem.
Two differences between yours and mine:
1. You are doing an update and not a mirror (as I am doing)
2. From what I can see your destination install.wim is newer than the source install.wim so it would not want to update it.
This is ...

You can see from the screen grab above that the files are identical and and that they are also matched by FFS.
I do indeed get an overwrite warning if I move via file explorer.
I have set up a fresh compare between a source and dest folders and get the same results shown here:
First screen grab is ...

I am looking at this old thread as I have a similar problem (see https://freefilesync.org/forum/viewtopic.php?t=10095) with files being copied that are above the Maximum File size set in the UI. See thread linked above for more details on this as it is not quite this straightforward.
I am not sure ...

I have set a max file limit of 201Mbytes on a FFS config that was a Mirror.
I had source files that were between approx 2-3Gbytes and there was no matching destination file. As expected they were not copied.
However I found when the destination folder has files with matching names (names were the ...