syncthing-stignore man page

syncthing-stignore — Prevent files from being synchronized to other nodes




If some files should not be synchronized to other devices, a file called .stignore can be created containing file patterns to ignore. The .stignore file must be placed in the root of the folder. The .stignore file itself will never be synced to other devices, although it can #include files that are synchronized between devices. All patterns are relative to the folder root.


Note that ignored files can block removal of an otherwise empty directory. See below for the (?d) prefix to allow deletion of ignored files.


The .stignore file contains a list of file or path patterns. The first pattern that matches will decide the fate of a given file.


Prefixes can be specified in any order (e.g. “(?d)(?i)”), but cannot be in a single pair of parentheses (not “(?di)”).


Given a directory layout:

My Pictures/

and an .stignore file with the contents:

(?i)my pictures

all files and directories called “foo”, ending in a “2” or starting with “qu” will be ignored. The end result becomes:

.DS_Store     # ignored, will be deleted if gets in the way of parent directory removal
foo           # ignored, matches "foo"
foofoo        # synced, does not match "foo" but would match "foo*" or "*foo"
bar/          # synced
    baz       # synced
    quux      # ignored, matches "qu*"
    quuz      # synced, matches "qu*" but is excluded by the preceding "!quuz"
bar2/         # ignored, matched "*2"
    baz       # ignored, due to parent being ignored
    frobble   # ignored, due to parent being ignored; "!frobble" doesn't help
My Pictures/  # ignored, matched case insensitive "(?i)my pictures" pattern
    Img15.PNG # ignored, due to parent being ignored

Please note that directory patterns ending with a slash some/directory/ matches the content of the directory, but not the directory itself. If you want the pattern to match the directory and its content, make sure it does not have a / at the end of the pattern.

Effects on “in Sync” Status

Currently the effects on who is in sync with what can be a bit confusing when using ignore patterns. This should be cleared up in a future version…

Assume two devices, Alice and Bob, where Alice has 100 files to share, but Bob ignores 25 of these. From Alice’s point of view Bob will become about 75% in sync (the actual number depends on the sizes of the individual files) and remain in “Syncing” state even though it is in fact not syncing anything (issue #623 <>). From Bob’s point of view, it’s 100% up to date but will show fewer files in both the local and global view.

If Bob adds files that have already been synced to the ignore list, they will remain in the “global” view but disappear from the “local” view. The end result is more files in the global folder than in the local, but still 100% in sync (issue #624 <>). From Alice’s point of view, Bob will remain 100% in sync until the next reconnect, because Bob has already announced that he has the files that are now suddenly ignored.


The Syncthing Authors

Referenced By


Jan 14, 2019 v1 Syncthing