LoliSnatcher is a Dart booru client with parallel search tabs

Tabs are the core idea, not a feature list

LoliSnatcher is a client for booru imageboards, and the tagline describes it as a place to view images and videos and do batch downloads from many booru sites with extensive customization. What stands out among the features is the tabs system. The description calls it an extensive tabs system where you can run multiple searches simultaneously with independent tab sessions, each with its own booru, tags and scroll position, and there is a tabs manager with detailed filters for searching across all of your tabs. That is a different model from the usual imageboard client, where you pick one site, one query and page through the results. A person who watches several communities at once, or who wants to compare how a tag is used across sites, is the one this is built for. The other features follow the same logic. Tag management covers favourites, filters, blacklists and tag history, sync carries favourites and settings across multiple devices, and customization is described as deep settings for the interface and behaviour, with themes, layouts and image scaling among them. The privacy position is stated as no data collection with all data stored locally, and there is a separate privacy policy file in the repository.

The engine list is the product, and it is long

The supported platforms list is the most informative part of the README. It includes Danbooru, Gelbooru, GelbooruV1 for Booru.org, Moebooru, Philomena, Shimmie, e621, Szurubooru, the Hydrus Network, Sankaku in its default and Idol variants, rule34.xyz and rule34.world, rule34hentai, Booru On Rails also known as Twibooru, InkBunny, AGNPH, FurAffinity, Realbooru, RainBooru, r34world and xyz, and the description closes with and more. The topics on the repository line up with that list, covering danbooru, gelbooru, inkbunny, moebooru, philomena, sankaku, sankakuchannel, shimmie, shimmie2, szurubooru, booru and booru-client. The consequence for a user is straightforward. If the sites you use are in that list, the app is immediately useful, and if they are not, there is no configuration that will add them, so the check happens before the install rather than after it. The project asks for contributions of new booru platform support specifically, alongside bug fixes, translations and documentation improvements, which tells you the engine set grows by request rather than by configuration.

Flutter, with the localisation tooling to match

The app is built with Flutter, and the primary language is Dart, with the repository carrying the usual Flutter project markers, an android/ directory, a linux/ and a windows/ directory, a pubspec.yaml with a pubspec.lock, an analysis_options.yaml and a .fvmrc for pinning the Flutter SDK version. The release history shows a steady stream of hotfix versions, with 2.5.2 Hotfix 1 on 2026-07-31, 2.5.1 Hotfix 1 on 2026-05-28 and 2.5.0 Hotfix 2 on 2026-03-30, and the last push on 2026-10-18. Distribution is broad for a side project, with a Google Play listing under the package com.noaisu.play.losn, GitHub releases, and a badge for IzzyOnDroid pointing at apt.izzysoft.de, which is the F-Droid style channel that serves users without the Play Store. The repository also has a fastlane/ directory, which is the release automation for the store listings, and a build.sh for local builds.

Translation runs through POEditor and a set of helper scripts

Localisation is taken seriously enough to have its own tooling and its own directory of scripts. The project says it is working on translating the app to other languages using POEditor, and invites people to get in touch there or in the Discord server, with a link to the project on that service. The repository backs that up with a set of Dart scripts at the top level named loc_analyze.dart, loc_apply.dart, loc_build.dart and loc_cleanup.dart, plus a loc_watch.sh, and a slang.yaml file that configures the translation tooling. A slang.yaml at the root of a Flutter project is the marker of a specific setup, and the four loc scripts with distinct names suggest a pipeline with separate steps for analysis, applying, building and cleaning rather than a single command. The README asks contributors to read the localization guide section of CONTRIBUTING.md before submitting translations, which is a sensible guard against a stale localisation. The wiki/ directory holds the screenshots and presumably the documentation, and the scripts/ directory sits alongside it.

What to check before you install it

A few things decide whether this is a good fit. First, the engine list, since it is the difference between a useful app and an unused one. Second, the distribution channel, since a Play Store build, a GitHub release and an IzzyOnDroid package are not identical and the last is the one for anyone outside the Google ecosystem. Third, the batch download behaviour, because a client that can pull from many sites in parallel will saturate a connection and hit rate limits on sites that dislike it, and the README does not document any throttling behaviour, so that is a question to answer from the documentation or the Discord rather than assume. Fourth, the privacy claim, which is stated as no data collection with all data stored locally, with a privacy policy file in the repository and a link in the Links section, and it is worth reading rather than taking the summary at face value. The licence is the GNU Affero General Public License v3.0, which is the copyleft licence with the network use clause, so if you intend to modify and serve the app, that term is the one to read carefully.

Editorial conclusion

Adopt LoliSnatcher when you follow several imageboards and want one app that runs searches side by side, downloads in batches and keeps favourites on your own devices. Do not adopt it as a general purpose gallery, since the engine set is fixed to the sites the app implements. Verify first which of your sites are in the supported list, since a missing engine is not a configuration you can add, that the batch download limits suit your connection, and that you have read the privacy policy linked in the repository, since the no data collection claim is the app's own.

Frequently asked questions

Official sources

1. Issues
2. License: AGPL-3.0
3. NO-ob/LoliSnatcher_Droid on GitHub
4. README
5. Releases