Compress JPEG, PNG, and WebP images directly from the IntelliJ IDEA Project view, powered by TinyJPG.
JetBrains Marketplace · GitHub Releases · Changelog
Install from the TinyJPG Compressor plugin page, or from the IDE:
- Open Settings / Preferences → Plugins → Marketplace.
- Search for TinyJPG Compressor.
- Click Install and restart the IDE if prompted.
- Open GitHub Releases.
- Download the plugin ZIP from the release's Assets section, not the source code archive.
- Open Settings / Preferences → Plugins → ⚙ → Install Plugin from Disk….
- Select the downloaded ZIP without extracting it, and restart the IDE if prompted.
End users do not need to install a separate JDK; the plugin runs on the IDE's bundled runtime.
- Select image files or directories in the Project view.
- Right-click and choose TinyJPG Compress.
- Monitor progress and results in the TinyJPG Console tool window at the bottom of the IDE.
- Check the completion notification for the number of successful and failed files.
Images are uploaded to TinyJPG for compression, and successful results replace the original files in place. Keep a backup or commit your images to version control before compressing them.
- Supports
.jpg,.jpeg,.png, and.webpimages. - Recursively collects images from selected directories.
- Skips unsupported files and images larger than 5 MB.
- Processes up to two images concurrently.
- Displays progress, size changes, and errors in a dedicated console.
- Uses atomic file replacement when saving compressed images.
- JDK 21.
- Internet access to download Gradle, the IntelliJ Platform SDK, and build dependencies.
The project uses the Gradle wrapper and builds against IntelliJ IDEA 2025.3.3. A separate Gradle installation is not required.
macOS / Linux:
./gradlew buildPluginWindows PowerShell:
.\gradlew.bat buildPluginThe plugin ZIP is generated in build/distributions/. Install it using Install Plugin from Disk… as described above.
macOS / Linux:
./gradlew runIdeWindows PowerShell:
.\gradlew.bat runIdeThe release workflow is triggered manually:
- Update the project version in gradle.properties and the Changelog, then push the changes.
- Run the workflow on the intended branch, providing a matching tag such as
v1.0.1and a release description. - The workflow builds the plugin, creates and pushes the tag, and publishes a GitHub Release with the plugin ZIP.
Pushing a commit alone does not trigger this workflow. The workflow does not publish to JetBrains Marketplace.
To publish to Marketplace, configure publishToken in your user-level ~/.gradle/gradle.properties, or set the PUBLISH_TOKEN environment variable. Never commit the token to the repository.
./gradlew publishPluginOn Windows, use .\gradlew.bat publishPlugin.
MIT