Image Toolbox: an Android image editor built in Kotlin and Jetpack Compose

What Image Toolbox solves, and who it is actually for

Most photo editing on Android happens inside apps that want an account, a subscription, or a network connection. Image Toolbox takes the opposite position. The README describes it as "a versatile image editing tool designed for efficient photo manipulation" and lists crop, filters, EXIF editing, background erasure and AI enhancement as the core jobs. The repository topics add OCR recognition, PDF, PSD, JXL, QR code scanning, photo collage and upscaling to that list.

The intended audience is stated plainly: "Ideal for both photographers and developers". That second group is worth pausing on. A developer who needs to batch-process images on a phone, inspect EXIF before publishing, or run OCR on a screenshot without uploading it anywhere has a genuine use case here. The app is Android-only. The README badge says Api 24+, so anything older than Android 7.0 is out. There is no desktop build in the repository layout: the top-level entries are app/, core/, feature/, lib/, benchmark/ and build-logic/, which is the shape of a Gradle multi-module Android project, not a cross-platform one.

How the Kotlin and Jetpack Compose codebase is organised

The module split is the most informative thing about this project. app/ holds the Android application, core/ holds shared logic, feature/ holds individual editing capabilities, lib/ holds third-party or vendored code, and benchmark/ holds performance tests. build-logic/ is a convention plugin directory, which means build configuration is shared across modules rather than repeated in each build.gradle.kts. That is a deliberate choice for a project with this many features: a new filter or format handler lands in feature/ and inherits the same compiler and dependency setup.

The UI stack is declared on the README badges: Kotlin, Jetpack Compose, and Material You. Material You means the app can follow the system wallpaper palette on Android 12 and later, which is a visual decision rather than a functional one, but it explains why the screenshots in fastlane/ look different from a fixed-theme editor. The repo also carries ARCHITECTURE.md and ARCHITECTURE_2 at the top level. Those files are the right place to start if you plan to contribute, because the module graph is not obvious from the directory names alone.

One thing the README does not give is a processing pipeline description. It says the app can erase backgrounds and enhance images "with AI", but it does not name a model, a runtime, or whether that work happens on-device or through a remote call. If offline operation matters to you, that is a question to answer by reading the code, not the README.

Installing Image Toolbox on Android

There is no build-from-source tutorial in the README. The documented distribution channels are the Google Play listing and F-Droid, both under the package name ru.tech.imageresizershrinker. If you want the app on a device, install it from one of those two sources rather than compiling it.

The README links to https://f-droid.org/packages/ru.tech.imageresizershrinker for the F-Droid build and to https://play.google.com/store/apps/details?id=ru.tech.imageresizershrinker for the Play build. Both use the identical package name, so the F-Droid client and the Play client resolve the same identifier.

Building from source is possible in principle, since the repository ships gradlew and gradlew.bat plus a settings.gradle.kts and build.gradle.kts at the top level. The README does not document the build, so treat the checked-in wrapper as the entry point and expect to supply your own Android SDK and signing configuration.

The README does not state the required JDK version, the Android Gradle Plugin version, or whether a release build needs extra signing keys. Those are gaps you would have to close by reading gradle/ and build-logic/ yourself.

Where Image Toolbox is the wrong tool

The clearest limitation is platform. The RELATED SEARCHES list includes "image toolbox for windows", "image toolbox pc" and "image toolbox ios", and the repository gives no basis for any of them. The README badges name Android and API 24+, the project is a Gradle Android build, and the distribution links are Play and F-Droid. Anyone searching for a Windows or iOS build is looking for something this project does not provide.

The second limitation is the missing API surface. Image Toolbox is an application, not a library. Nothing in the README or the top-level layout suggests a published artifact you can depend on from another Android project. If your goal is to call a crop or OCR routine from your own Kotlin code, you would be reading and copying source from feature/ modules rather than adding a dependency.

The third is documentation depth. The README is a feature showcase with badges, screenshots and store links. It does not describe the AI enhancement path, does not document rollback or version pinning for F-Droid installs, and does not explain how EXIF edits interact with the various output formats the topics list. For a tool that touches metadata, that last point deserves a direct answer in the docs and does not get one.

Image Toolbox compared with Snapseed

Snapseed is the comparison people search for, and the difference is not feature count. Snapseed is a closed-source Google editor built around a fixed set of adjustment tools: healing, selective edits, curves, perspective. Image Toolbox is Apache-2.0 and built around a much wider, more utilitarian set: OCR, QR scanning, PDF handling, PSD, JXL, collage, upscaling, EXIF editing.

That breadth is the point. If your task is retouching a single photograph with fine tonal control, Snapseed's toolset is narrower and more polished for that job. If your task is converting a batch of images, reading text out of a screenshot, or stripping metadata before sharing a file, Image Toolbox covers ground Snapseed does not attempt. The licence difference also matters for anyone who wants to inspect or fork the code: Apache-2.0 permits that, and a closed-source app does not.

The trade-off runs the other way too. A project that ships crop, filters, OCR, PDF, PSD, JXL, QR, collage and upscaling in one Android app has a large surface to keep working, and the README gives no compatibility matrix for which formats survive which operations. Snapseed's narrower scope is easier to trust for the specific edits it does.

Releases, licence and the cost of keeping up

The project is not archived, and the last push was on 2026-09-15. Release 4.2.0 is dated 2026-09-04, preceded by 4.2.0-rc10 and 4.2.0-rc09 in August 2026. That cadence, with multiple release candidates before a stable tag, tells you the maintainer ships in stages and expects testers to run pre-releases. If you install from F-Droid, you inherit whatever version that repository has built, which may lag the GitHub release.

The licence is Apache-2.0, and the repository carries a LICENSE file at the top level. Apache-2.0 permits commercial use, modification and redistribution, and it includes an explicit patent grant. It also requires that you preserve the licence and notice files and state significant changes if you redistribute a modified version. That is a summary of the licence text, not legal advice; read LICENSE and, for a commercial redistribution, get your own review.

Upgrade cost is mostly the Android version floor. API 24+ is the stated requirement, so the app targets a wide device range, but each release can raise that floor or change which formats are supported. The README does not document a changelog policy or a deprecation process, so the release notes on GitHub are the only place to check before upgrading a device fleet.

Editorial conclusion

Adopt Image Toolbox if you want an offline, Apache-2.0 Android editor for crop, filters, EXIF, OCR and background removal, and you are willing to install it from F-Droid or the Play listing under the package name ru.tech.imageresizershrinker. Do not adopt it if you need a Windows, web or iOS build, or if you require a stable API surface for scripting, since the README describes a user-facing app rather than a library. Before committing, verify the current release on the GitHub releases page, confirm your device runs Android API 24 or newer, and check that the licence text in LICENSE matches how you intend to redistribute the app.

Frequently asked questions

Official sources

1. Issues
2. License: Apache-2.0
3. README
4. Releases
5. T8RIN/ImageToolbox on GitHub