ripme

RipMe

About

RipMe is an album downloader (or "ripper") for various websites. This is a cross-platform tool that runs on your computer. Works on Windows, Linux, and Mac.

Download

Download ripme.jar from the latest release. For information about running the .jar file, see the How To Run wiki.

Minimum Requirements

Requires Java 21 or later to run. RipMe has been tested on and is confirmed working on Windows, Linux, and Mac.

Java 21 is the most modern possible Java version that allows us to support the most platforms; it's the default JDK on current Debian stable. See thread and issue #2055.

Supported Sites

Jump to:

• List of Supported Sites
• Site Not Supported?

Recent development updates

• The current active development repo for RipMe is located at ripmeapp/ripme.
• Note: For a while, the ripmeapp/ripme repo was inactive, but development continued at ripmeapp2/ripme.
• Now, maintainers have been updated and development has been rejoined with ripmeapp/ripme where it will continue.
• You may find a number of stale issues on ripmeapp/ripme and/or on ripmeapp2/ripme until everything is merged back together and statuses are updated.

Maintainers

RipMe has been maintained with ♥️ and in our limited free time by the following people, with current expected activity level marked by color of the indicator:

• @MetaPrime 🟡 (2025–present)
• @soloturn 🟡 (2021–present)
• @cyian-1756 🟥 (2017–2020)
• @kevin51jiang 🟥 (2017–2018)
• @MetaPrime 🟡 (2016–2017)
• and its original creator, @4pr0n 🟥 (2014–2016)

If you'd like to become a maintainer, reach out on https://gitter.im/RipMeApp/Lobby and ask an active maintainer to be added to the team.

Contact

Chat with the team and community on gitter and reddit.com/r/ripme

Version Numbers

The version number like ripme-1.7.94-17-2167aa34-feature_auto_release.jar contains a release number (1.7.94), given by a person, the number of commits since this version (17). The commit SHA (2167aa34) uniquely references the source code ripme was built from. If it is not built from the main branch, the branch name (feature/auto-release) is given.

Note that this follows the Semantic Versioning spec (see https://semver.org/), and uses the feature of the format that adds extra data after the - to provide helpful context so that every commit on every branch has a dintinct semver version associated with it.

Installation

On macOS, there is a cask.

brew install --cask ripme && xattr -d com.apple.quarantine /Applications/ripme.jar

Changelog

Changelog (ripme.json)

Features

• Quickly downloads all images in an online album. See supported sites
• Easily re-rip albums to fetch new content
• Built in updater
• Skips already downloaded images by default
• Can auto skip e-hentai and nhentai albums containing certain tags. See here for how to enable
• Download a range of urls. See here for how

List of Supported Sites

See the full list of Supported Sites in the wiki.

Note: Websites change over time and therefore rippers, which fundamentally depend on website layouts, can break at any time. Feel free to open an issue if you notice something not working, but please search the list of issues to see if it's already been reported.

The list of supported rippers includes:

• imgur
• twitter (currently broken, needs to be updated for X)
• tumblr
• instagram
• flickr
• photobucket
• reddit
• redgifs
• motherless
• imagefap
• seenive
• 8muses
• deviantart (currently broken by major changes to the site)
• xhamster
• xvideos
• ... and more!

Site Not Supported?

Request support for more sites by adding a comment to this Github issue.

If you're a developer, you can add your own Ripper by following the wiki guide: How To Create A Ripper for HTML Websites.

Maintainers

Compiling & Building

The project uses Gradle.

In particular, we use the gradlew script (gradlew.bat on Windows) to build the app and run tests.

To build the .jar file and run the appropriate tests, navigate to the root project directory and run gradlew with the appropriate commands (see below). Ensure that you manually test that your change works, add or update the corresponding test, and run at least the test(s) that are relevant to your change.

For example, if you modify the Xhamster ripper, you might run this or a similar command:

./gradlew clean build testAll --tests XhamsterRipperTest.testXhamster2Album

Here's a breakdown of the functionality of the gradlew scripts:

The build verb will build the .jar, the tests, and will also run the tests ,except for disabled and flaky tests.

Thus build and build test are actually synonymous.

./gradlew build
./gradlew build test

You can get more specific with your test commands:

./gradlew clean build testAll --tests XhamsterRipperTest.testXhamster2Album
./gradlew clean build -x test --warning-mode all

To perform a clean rebuild, which is only necessary to see warnings for unchanged files or if you believe that the incremental build is interfering with the build picking up your changes, for example. That shouldn't be an issue for gradle, so you should check for easier explanations like whether you saved your changes. :)

./gradlew clean

To build ("assemble") the .jar without running the tests, which is useful for manual verification of functionality of a work in progress, run the following:

./gradlew assemble

The generated JAR (java archive) in build/libs will include all dependencies.

Running Tests

Tests can be tagged as beeing slow, or flaky. The gradle build reacts to the following combinations of tags:

• default is to run all tests without tag.
• testAll runs all tests.
• testFlaky runs tests with tag "flaky".
• testSlow runs tests with tag "slow".
• tests can be run by test class, or single test. Use "testAll" so it does not matter if a test is tagged or not.
• tests can give the full stack of an assertion, exception, or error if you pass --info to the command

./gradlew test
./gradlew testAll
./gradlew testFlaky
./gradlew testSlow
./gradlew testAll --tests XhamsterRipperTest
./gradlew testAll --tests XhamsterRipperTest.testXhamster2Album
./gradlew testAll --tests ChanRipperTest --info

Please note that some tests may fail as sites change and our rippers become out of date. Start by building and testing a released version of RipMe and then ensure that any changes you make do not cause more tests to break.

Maintainers: How to Publish a New Release

See wiki: How to Make a New Ripme Release