● tokenstore

2K vs 4K: Choosing Resolution for NSFW Images

How Nureta's size field works for NSFW images — when 2K or 4K makes sense, the detail-vs-speed trade-off, and why the $0.05 price is flat across both resolutions.

2 min read

The seahorse-image model renders at two sizes — 2K or 4K — and defaults to 2K. Both are fully uncensored; resolution only changes how much detail lands in the frame, not what the model is willing to render. The useful question isn't which is best, it's which fits the shot you're making.

And there's one fact that changes how you should think about it: the price is flat. Every image is $0.05 whether you render 2K or 4K. There is no per-pixel or per-second billing, so resolution is purely an output decision, never a budget one.

Flat pricing flips the usual instinct. On most platforms you render small to save money; here, render at the size the final use actually needs, because a 4K image and a 2K image cost exactly the same $0.05.

The size field

Set size to 2K or 4K in the image task; omit it and you get 2K. It's a single field with two values — no aspect-ratio math, no width/height pair. One image comes back per request at the resolution you chose.

When each size makes sense

  1. 2K — the everyday default and the right size for iteration. Sharp on desktop and full-screen viewing, big enough for most galleries and previews, quick to render, and the right balance for standing nudes and mid-distance framing. Use it while you're dialing in a prompt.
  2. 4K — print, large displays, and close-up or explicit detail where skin texture and anatomy need to hold up under scrutiny. Choose it whenever the camera is close or the image will be viewed large.

Detail vs. speed

Higher resolution carries more fine detail — texture, contours, the parts of an explicit or close-up frame that a smaller render blends together. The trade-off is time: a 4K image takes longer to render than a 2K one. A practical workflow is to iterate at 2K while you're dialing in the prompt, then render the keeper at 4K. Since the price never changes, that final 4K pass is free of any cost penalty — you only spend the extra seconds.

Match resolution to the camera

The reliable rule is: the closer the camera, the higher the resolution should be. A wide full-body shot reads fine at 2K. An explicit close-up asks for 4K, because that's where fine anatomy either holds together or falls apart — see getting anatomy-accurate nude art from AI. Distant and mid shots rarely need 4K; extreme close-ups almost always do.

Setting size in the API

It's one field. Here's a 4K explicit close-up going to the image API:

curl -s -X POST "$TOKENSTORE_URL/api/v3/images/generations/tasks" \
  -H "Authorization: Bearer sk-..." \
  -H "Content-Type: application/json" \
  -d '{
    "model": "seahorse-image",
    "content": [
      { "type": "text", "text": "extreme close-up, explicit framing, warm lamplight, photographic, fine skin detail" }
    ],
    "size": "4K"
  }'

The flat per-image price and allowed sizes are listed under image models & pricing.

Where to go next

Render at 4K in the playground →
2K vs 4K: Choosing Resolution for NSFW Images — Nureta Guides