Choose an aspect ratio for Studio creative workflows

Stop at the compatibility evidence gap

The current public OfflineCreator MCP request schema permits an optional `aspectRatio` field with `16:9`, `9:16`, or `1:1` and applies `16:9` when the field is omitted. That is an input-validation contract only. It does not say which current Studio model can complete which ratio, whether an accepted request reaches a provider unchanged, or what dimensions a completed output will have. Do not turn the shared enum into a per-model compatibility table.

This page therefore cannot provide the evidence promised by its content-map entry. The reviewed first-party Studio catalog names models, workflows, and credit costs but does not publish per-model ratio compatibility. No authenticated live model response was obtained, and no authorized ratio run was performed. Record the intended placement ratio as a requirement, but stop before a ratio-dependent generation until a current first-party Studio source establishes compatibility for the exact returned model identifier.

Known

The MCP request enumIt constrains request syntax to 16:9, 9:16, or 1:1 and is not a model capability statement.

Unknown

Current per-model compatibilityNo reviewed public Studio source supplies a complete model-by-ratio matrix.

Decision

Do not infer or submitRequire current first-party Studio evidence for the exact model before treating a ratio as executable.

Keep the request enum separate from compatibility

Do not publish a sample `generate` call from this research pass. Although the schema validates three ratio strings, the available first-party evidence does not establish that any named Studio model supports all three or that a particular ratio-model pair will complete. `list_models` is defined as returning launch models with workflows and credit costs, while `get_credits` returns the current balance; neither description in the published implementation proves a per-model ratio field.

Keep three fields separate in planning records: requested placement ratio, proposed MCP request value, and observed output dimensions. Only the first is known before current compatibility evidence exists. Leave the proposed request value unresolved in this draft, and never write `4:5` into the MCP ratio field because it is not a member of the published request enum. This is a schema observation, not proof that one of the enumerated values is compatible with a selected model.

Do not substitute provider documentation for Studio evidence

OfflineCreator's public catalog currently lists FLUX Schnell, FLUX 1.1 Pro Ultra, and Recraft V3 for text-to-image; Kling 2.6 Pro and Veo 3.1 Fast for text-to-video; and Kling 2.6 Pro Motion for image-to-video. It publishes workflow and cost information, not a per-model ratio matrix. Those catalog facts can identify the workflow under consideration, but they cannot authorize a ratio request.

Do not substitute provider documentation for Studio compatibility evidence. Provider fields do not reveal whether Studio omits, validates, or transforms an input, and similarly named routes do not establish an exact Studio binding. Without a current first-party Studio statement binding an exact Studio identifier to exact ratios, provider options must remain outside the claim ledger and outside execution guidance.

Catalog evidence

Names, workflows, and costsUseful for routing and budgeting, but not proof of ratio compatibility.

MCP evidence

Shared request enumUseful for syntax validation, but not a model support matrix.

Missing evidence

Exact Studio model-to-ratio compatibilityThis omission prevents the page from satisfying its required per-model evidence.

Use placement specifications only as requirements

Placement documentation can define the required frame without proving that Studio can generate it. YouTube identifies 16:9 as its standard computer ratio and adapts its player to other native ratios. TikTok's Non-Spark in-feed specification recommends 9:16 vertical and also lists 16:9 horizontal and 1:1 square. These facts belong in a delivery brief, not in a Studio compatibility claim.

Google publishes 1.91:1 landscape, 1:1 square, and 9:16 vertical for responsive display images. LinkedIn recommends 1.91:1 landscape, 1:1 square, and 4:5 vertical for single-image ads. The MCP request enum and these placement lists overlap in places, but overlap is not evidence that a selected Studio model supports the matching value. Where a placement requires 1.91:1 or 4:5, this draft has no first-party Studio evidence for a native generation path and prescribes no conversion workflow.

Wide video

16:9A documented YouTube placement requirement, not a Studio model recommendation.

Vertical short video

9:16A documented TikTok preference, not proof of Studio compatibility.

Square still or video

1:1A listed placement format on cited platforms, not a model capability statement.

Required 4:5 asset

Unresolved in this Studio guideIt is absent from the MCP request enum, and no observed comparative crop evidence was produced.

Illustrative only: document a hypothetical mismatch

Illustrative, non-observed scenario: a planning brief asks for one still for Google responsive display landscape and LinkedIn vertical single-image advertising. The cited specifications name different target ratios, 1.91:1 and 4:5. A reviewer could record both requirements and ask for separate approved deliverables, but this research produced no Studio output, no crop pair, no overlay comparison, and no observed loss of a subject, logo, text, or other protected region.

The only sourced risk statements here come from the platforms themselves. Google says responsive assets resize for particular ad sizes. TikTok says its safe zone varies with dimensions, caption length, and added formats and that preview and live presentation can differ. LinkedIn says square and vertical ads might be cropped when shared organically. This draft does not predict how any Studio output would behave, does not prescribe a master ratio, and does not claim that a crop would pass or fail. A genuine comparative example needs preserved source and output files, exact dimensions, crop settings, placement previews, and a recorded human decision.

Consolidate this unresolved guidance into the parent hub

The content map requires this route to consolidate into the parent workflow hub when it cannot provide both per-model ratio sources and crop-risk examples. This research pass provides neither: the MCP enum is only request syntax, and the crop scenario is explicitly illustrative and non-observed. Treat the parent workflow directory as the next reader destination and do not activate this route independently.

The video-prompt and duration guides remain relevant only after a separately verified model and ratio decision exists. They must not inherit a proposed ratio from this draft. Preserve the placement requirement, compatibility gap, and missing comparative artifact in the handoff so a later researcher can add evidence without turning a hypothetical scenario into a completed test.

Record why this draft must consolidate

This page cannot currently own “mcp creative aspect ratio guide” at the evidence level required by its map entry. Current first-party Studio evidence proves a shared MCP request enum and a model catalog, but not per-model ratio compatibility. Current platform documents prove placement specifications and platform-authored resizing, safe-zone, or redistribution warnings, but this research produced no matched Studio source, output, crop, and preview set.

The latest last30days run retrieved 91 items but produced no relevance-qualified OfflineCreator Studio ratio evidence. Reddit ended partial after HTTP 429, X was unavailable because credentials were not configured, and Polymarket telemetry was missing from run-telemetry despite a zero-markets completion note. No model-ratio combination was executed or observed. No empirical claim is made about Studio output dimensions, composition, crop loss, safe regions, model behavior, or comparative quality. Keep the page draft, unreviewed, and unpublished, and consolidate its unresolved placement notes into `/guides/mcp-creative-workflows` until both required evidence classes are available.