NSFW Image Detector

Pricing

Rating

Developer

Actor stats

Categories

Share

What can NSFW Image Detector do?

This NSFW detector analyzes JPEG, PNG, BMP, and GIF images and categorizes them based on the following criteria:

• 🎨 Drawing: Harmless art, safe for kids
• 🐙 Hentai: Pornographic 18+ art, unsuitable for most work environments
• 😐 Neutral: General inoffensive content
• 🍑 Porn: Indecent 18+ content and actions, often involving genitalia
• 😏 Sexy: Provocative content, may include nipples

Fast ~250ms per single image and easy nude content classification comes with a pretty accurate ~93% probability!

*To start scrapping, please use at least one URL field

Results

You'll get a dataset containing the output of this actor. The length of the dataset will depend on the amount of results you've set/got. You can download those results as an Excel, HTML, XML, JSON, and CSV document or you can just use Apify API to get the data.

{
"image":"https://apify-image-uploads-prod.s3.amazonaws.com/Nbvb2ZAX96yhhtJQy/EQ2R5dkeB3Kizko6x-IMG_6685.png",
"status":true,
"resultType":"Neutral",
"neutral":0.99,
"drawing":0.01,
"hentai":0,
"porn":0,
"sexy":0
},{
"image":"https://xxx.gif",
"status":true,
"resultType":"Porn",
"neutral":0.1,
"drawing":0,
"hentai":0.01,
"porn":0.79,
"sexy":0.1
}

Why would I use NSFW Image Detector?

Content Moderation: NSFW image detector APIs are crucial for content moderation on platforms that allow user-generated content. By automatically identifying and flagging explicit or inappropriate JPEG, PNG, BMP, and GIF images, this nsfw detection API help maintain a safe and suitable environment for all users. It enables platforms to proactively filter out potentially offensive, unsuitable, or harmful content.

Compliance with Regulations and Policies: Many jurisdictions and online platforms have strict policies and regulations regarding the display and distribution of explicit or adult content. NSFW image detector assists platforms in adhering to these guidelines by automatically preventing the dissemination of inappropriate images, ensuring compliance, and avoiding legal or reputational issues.

Enhanced User Experience: Implementing this API enhances the overall user experience on platforms that involve sharing or browsing visual content. By filtering out explicit or NSFW images, platforms can provide users with a more pleasant and appropriate browsing experience, increasing the likelihood of user engagement and longer platform usage.

Data Quality and Relevance: Scrapers are commonly used to gather information from various sources, including images. However, when scraping data, there's a risk of inadvertently collecting explicit or NSFW images that may not be suitable for the intended purpose or audience. By utilizing an NSFW image detector API, you can filter out inappropriate images during the scraping process, ensuring that the collected data maintains a high level of quality, relevance, and appropriateness.

Integrations and NSFW Image Detector

NSFW Image Detector can be connected with almost any cloud service or web app thanks to integrations on the Apify platform. Integrate with Make, Zapier, Slack, Airbyte, GitHub, Google Sheets, Google Drive, and more. Or you can use webhooks to carry out an action whenever an event occurs, e.g. get a notification whenever Content Checker successfully finishes a run.

Using NSFW Image Detector with the Apify API

The Apify API gives you programmatic access to the Apify platform. The API is organized around RESTful HTTP endpoints that enable you to manage, schedule, and run Apify actors. The API also lets you access any datasets, monitor actor performance, fetch results, create and update versions, and more. To access the API using Node.js, use the apify-client NPM package. To access the API using Python, use the apify-client PyPI package.Check out the Apify API reference docs for full details or click on the API tab for code examples.

Your feedback

We’re always working on improving the performance of our Actors. So if you’ve got any technical feedback for xxx or simply found a bug, please create an issue on the Actor’s Issues tab in Apify Console.