Skip to content

Search

Introduction

The main feature of Grabber is to search images, and as such, many things can impact the results you see.

Search field

What is written in the main search field will usually be passed as-is to the source, so depending on your source, the search syntax might be different.

You should check on the source which syntax they accept, but in most cases, all you have to do is separate each tag with a space.

Post-filter

Introduction

Sometimes, a source does not allow you to use a given syntax or limits the number of terms you can use.

In this case, the best solution is to use a post-filter, which loads the results from the source using your search and then filters them with another search.

Warning

If your post-filter is too specific, all images might get filtered and Grabber will show zero results!

Syntax

Post-filtering uses the most popular search syntax in boorus, which is:

  • Separate tags by spaces to make an "AND" (ex: tag1 tag2)
  • Prefix a tag or a filter by a caret (-) to negate it (ex: -tag)
  • field:value to filter by a token (ex: rating:safe), the list of tokens can be found on the Filename page
  • field:>value to filter by a token value using a comparison (ex: id:>1000), you can use any of these operators: >, >=, <, <=
  • field:from..to to filter by a range (ex: date:2019-09-02..2019-09-07)

Special "grabber" token

A special token is generated by Grabber for images to be used by post-filters. It allows to filter on a few special values:

  • grabber:alreadyExists if an image already exists on the disk
  • grabber:inMd5List if an image's MD5 is already present in the global MD5 list
  • grabber:downloaded if either grabber:alreadyExists or grabber:inMd5List is true
  • grabber:favorited if the image's tags contain a favorited tag
  • grabber:monitored if the image's tags contain a monitored tag

In addition, two tokens about Grabber version are available:

  • grabber_branch: "release" for official releases, or "nightly" for the dev version
  • grabber_version: the version code (ex: "1.2.3") for official releases, or the first 8 characters of the commit hash for the dev version

Blacklist

Introduction

You can blacklist some tags or combinations of tags to not see them in the results.

It can be edited in the settings in the "Save > Blacklist" category, or tags can be added to the blacklist by right-clicking on them and selecting "Blacklist".

Note:

  • Blacklist is a post-filter: it is applied after results are returned from the sources.
  • When using the CLI, images that contains blacklisted tags will no be downloaded unless the --blacklist option is used.
  • When using the GUI, images that contain blacklisted tags will not be downloaded unless explicitly selecting them and clicking 'save'.

Syntax

Each line of the blacklist corresponds to a combination of tags and uses the same syntax as post-filters.

Example

Given this blacklist: 

tag1
tag2 tag3
tag4 rating:safe

An image will be considered as "blacklisted" if either of those three conditions is met:

  • The image contains the "tag1" tag
  • The image contains both the "tag2" and "tag3" tags
  • The image contains the "tag4" tag and its rating is "safe"