Skip to content

Vertical storytelling

A webtoon API for vertical story workflows.

A webtoon API request combines tall output dimensions, serialized page structure, character references, and scene instructions for vertical reading products.

The API generates original assets. It does not provide a catalog of hosted webtoons, chapters, or creator metadata.

Generate a vertical example

Account, API key, usage, and billing open on LlamaGen.AI.

Direct answer

The decision this page is for.

Last verified:

A webtoon workflow uses tall canvases, multi-page pagination, and character references so a product can compose a vertical episode. The API generates original assets; it is not a hosted webtoon catalog.

Verifiable request

Two-page vertical episode

cURL
curl -X POST \
  https://api.llamagen.ai/v1/comics/generations \
  -H "Authorization: Bearer $LLAMAGEN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "prompt": "A vertical fantasy episode where Mina follows a glowing fox into a subway portal.",
  "size": "1024x1792",
  "pagination": {
    "totalPages": 2,
    "panelsPerPage": 4
  },
  "comicRoles": [
    {
      "name": "Mina",
      "dress": "yellow raincoat",
      "referenceImages": [
        "https://example.com/mina-front.webp"
      ]
    }
  ]
}'

Structured response

State your application can route

response.jsonPROCESSED
{
  "id": "gen_abc123",
  "status": "PROCESSED",
  "comics": [
    {
      "page": 0,
      "panels": [
        {
          "panel": 0,
          "caption": "Mina steps through the portal.",
          "assetUrl": "https://cdn.llamagen.ai/comics/panel-1.webp"
        }
      ]
    }
  ]
}

Format visualization

Vertical storytelling composed for a phone screen.

The mobile composition emphasizes tall canvases, scroll rhythm, episode structure, and continuity across separated scenes.

A creator scrolling a tall mobile webtoon episode with vertically spaced scenes and recurring characters
Editorial illustration of a vertical webtoon workflow; it is not a generated API result.Art direction · Contemporary vertical webtoon

Capability and boundary facts

Facts an integration can verify.

Last verified:

Endpoint
POST /v1/comics/generations
Authentication
Bearer API key
Lifecycle
QUEUED → PROCESSING → PROCESSED or FAILED
Delivery
Poll by generation ID or use a callback URL
Vertical format
Tall canvas plus multi-page pagination

Good fit

Use it when

  • Vertical comic apps
  • Serialized creator workflows
  • Mobile-first visual stories

Wrong fit

Do not use it for

  • Reading or indexing published webtoons
  • One-shot synchronous rendering
  • Unreviewed automated publishing

Production limits

Plan for the boundaries.

  • 01Episode pacing, gutters, and mobile reading rhythm require product-side layout review.
  • 02Do not combine fixed panel count with pagination in one request.
  • 03Generation is asynchronous; production interfaces must handle processing and failure states.
  • 04Outputs should be reviewed against product, brand, safety, and print requirements before delivery.
  • 05You must have the rights to prompts, photos, scripts, and reference assets submitted to the API.

Authoritative sources

LlamaGen API documentationOpenAPI specificationCurrent pricingTermsService status

Questions

Direct answers before you integrate.

01What size should I send for vertical reading?
Use a tall canvas such as 1024x1792 and pagination with totalPages and panelsPerPage. Do not also send fixPanelNum on the same request.
02Does the API host webtoon episodes for readers?
No. You store, layout, and present the returned assets in your own reader or CMS.
03How do I keep a character stable across an episode?
Pass named comicRoles with reference images on every page batch, then review continuity before you assemble the episode.

Related evaluation paths

FormatStory-to-Comic API for Scripts and Story BriefsFormatCharacter Consistency API for Multi-Panel ComicsSolutionComic API for Publishing Workflows

Next step

Move from evidence to a real API request.

LlamaGen provides the playground, API key, usage, billing, and authoritative service documentation.

Generate a vertical example