← back to catalog · registered 2026-08-22 13:56

Felldude/Qwen3-VL-8B-Instruct-Uncensored-V2

Felldude Qwen 8.8B
Your rig guess connected
? Why do I need an app?
Reading your rig…

This is a rough estimate. Install the free app - we'll show exact numbers.

Reading real hardware from your app right now. Numbers below are exact.

Below is the per-quantization compatibility for this model.

curl -H "Authorization: Bearer $ABL_KEY" \
     "https://abliteration.org/api/v1/models/Felldude%2FQwen3-VL-8B-Instruct-Uncensored-V2"
Response includes
  • classification m-uncensored
  • files 11
  • hub_downloads_all_time 2,777
  • author_summary 14 models
  • readme_text full
10 credits · hourly refresh · ~4 KB payload Get an API key →
Abliteration classifier · v1.0.0
M-U
Primary method

Uncensored (method unknown)

No other method signals detected in this model.
Confidence
LOW
Why this label 3 signals
Weak or ambiguous signals. Best guess based on catalog patterns; treat as tentative and check the evidence below.
  • 'uncensored' in name/tags but no 'abliterated' marker
  • method not identifiable from author declaration alone
  • may be DPO fine-tune, prompt engineering, or unknown technique
Refusal direction extraction

No specific extraction method could be identified for this model. The producer either did not document it or used a proprietary pipeline.

What is a refusal direction? →
Downloads · lifetime
3K
621 last 30d - stable
Likes
10
Descendants
2
in 2 direct forks
Model age
6mo ago
created 2026-03-17
Downloads over time
Now3.3K→from32↑10,066%
01.2K2.4K3.6K32 on Mar 183.3K on Oct 11MarAprMayJunJulAugSepOct
Mar 18 → Oct 11 · 69 snapshots · spans 207 days

Genealogy 2 direct forks

Full fork graph →

This model's place in the market. Above: what it was derived from. Below: the tree of everything derived from it.

Metadata

License
apache-2.0
Languages
en es ja
Tags
safetensors qwen3_vl en es ja license:apache-2.0 region:us

Related

Total size
16.3 GB
Files
11
Quantizations
1
Registered
2026-08-22 13:56
Last updated on HF
2026-09-30 21:36

Files by quantization

Auxiliary files 11 files 16.3 GB
model.safetensors 16.3 GB 2e02077a download
tokenizer.json 6.71 MB c6cc1014 download
vocab.json 2.65 MB 4783fe10 download
tokenizer_config.json 10.6 KB d3d37632 download
chat_template.json 5.37 KB 1081bacf download
README.md 3.05 KB e90119c7 download
.gitattributes 1.48 KB a6344aac download
config.json 1.44 KB 0e2df614 download
preprocessor_config.json 390 B 2ea84a43 download
video_preprocessor_config.json 385 B 3ba673a5 download
generation_config.json 269 B e116347d download

README current version from Hugging Face


license: apache-2.0
language:

  • en
  • es
  • ja

Notes

Version 2 - This version is highly attuned to NSFW content. However do to image only training it may generate some video captions as image.

This version requires 24GB or more VRAM.

  • Full finetune of the 8B parameter model (vision encoder frozen).
  • Training used Adam8bit due to model size (BF16/TF32 otherwise).
  • If used for NSFW captioning, leaving the prompt unchanged is recommended.

Prompt

Describe this image or video in English

No special prompting is needed, and you may use any of the following.

"Write a straightforward caption for this image. Begin with the main subject and medium. Mention pivotal elements—people, objects, scenery—using confident, definite language. Focus on concrete details like color, shape, texture, and spatial relationships. Show how elements interact. Omit mood and speculative wording. If text is present, quote it exactly. Note any watermarks, signatures, or compression artifacts. Never mention what's absent, resolution, or unobservable details. Vary your sentence structure and keep the description concise, without starting with “This image is…” or similar phrasing."

Include information about lighting.
Include information about camera angle.
Include information about whether there is a watermark or not.
Include information about whether there are JPEG artifacts or not.
If it is a photo you MUST include information about what camera was likely used and details such as aperture, shutter speed, ISO, etc.
Do NOT include anything sexual; keep it PG.
Do NOT mention the image's resolution.
You MUST include information about the subjective aesthetic quality of the image from low to very high.
Include information on the image's composition style, such as leading lines, rule of thirds, or symmetry.
Do NOT mention any text that is in the image.
Specify the depth of field and whether the background is in focus or blurred.
If applicable, mention the likely use of artificial or natural lighting sources.
Do NOT use any ambiguous language.
Include whether the image is sfw, suggestive, or nsfw.
ONLY describe the most important elements of the image.
If it is a work of art, do not include the artist's name or the title of the work.
Identify the image orientation (portrait, landscape, or square) and aspect ratio if obvious.
Use vulgar slang and profanity, such as (but not limited to) "fucking," "slut," "cock," etc.
Do NOT use polite euphemisms—lean into blunt, casual phrasing.
Include information about the ages of any people/characters when applicable.
Mention whether the image depicts an extreme close-up, close-up, medium close-up, medium shot, cowboy shot, medium wide shot, wide shot, or extreme wide shot.
Do not mention the mood/feeling/etc of the image.
Explicitly specify the vantage height (eye-level, low-angle worm’s-eye, bird’s-eye, drone, rooftop, etc.).
If there is a watermark, you must mention it.
Your response will be used by a text-to-image model, so avoid useless meta phrases like “This image shows…”, "You are looking at...", etc.

README history 3 versions

The author's README evolved over time. Click a version to see its content at that point.

  1. 2026-03-17Update README.md75c887e3 KB
    Loading...
  2. 2026-03-17Update README.md88d55893.1 KB
    Loading...
  3. 2026-03-17initial commita334a0328 B
    Loading...

Discussions 1 thread

  1. 2026-08-16cant use it in ai toolkit please helpopen3 💬#1
    Loading...
Catalog is the map. Apps are the tools.

Run models on your own machine, not in the cloud.

Every model page has an "Open in Abliteration" button that hands the model directly to the first-party desktop client, at the quantization your rig can actually run. No API keys, no subscription, no prompt leakage.

Open in Abliteration