Generate podcast cover concepts from the CLI
Explore square cover directions with a repeatable prompt structure.
Start with 20 free creditsRun a square concept pass from the CLI
Start by listing models and checking the account balance, then generate one square concept with an explicit model, prompt, aspect ratio, and bounded wait. The published 0.1.2 CLI accepts models, balance, and generate commands. Its generate path reads --model, --prompt, --aspect or --aspectRatio, and --wait; only 16:9, 9:16, and 1:1 are accepted aspect values.
A practical command is `npx @offlinecreator/mcp generate --model flux-schnell --prompt "Editorial podcast cover concept, one bold central symbol, dark navy field, warm coral accent, generous title area, no lettering" --aspect 1:1 --wait`. Keep the API key in the documented environment configuration, never in the prompt or command arguments. Save the CLI's JSON response alongside the prompt so the concept can be reviewed before another paid run.
- Discover
- npx @offlinecreator/mcp modelsRead the current image-model catalog and published credit costs before choosing a model.
- Preflight
- npx @offlinecreator/mcp balanceConfirm that the available balance covers the selected concept run.
- Generate
- --model flux-schnell --aspect 1:1 --waitName the model and square ratio explicitly; do not rely on the CLI's omitted-ratio behavior.
Choose the cost of the exploration pass
OfflineCreator's current image catalog prices FLUX Schnell at 1 credit, Recraft V3 at 5 credits, and FLUX 1.1 Pro Ultra at 8 credits. Use those values as a preflight budget, not as a quality score. A low-cost FLUX Schnell pass is suitable for testing whether the symbol, palette, and negative space communicate the show. Move to another model only when its stated fit matches the direction you need.
Set a stop condition before generating: one initial concept, one materially different alternative if the first misses the brief, then a human selection. Do not spend additional credits merely to vary tiny adjectives. The output is a concept asset, and the final cover still needs typography, rights, format, and small-size checks.
Match square support to the visual job
Studio's image generator currently presents FLUX Schnell, FLUX 1.1 Pro Ultra, and Recraft V3 with 16:9, 9:16, and 1:1 choices. The public fal endpoint documentation for FLUX Schnell separately exposes square and square_hd image-size values. These sources establish square support; they do not establish that one model will produce a better podcast cover than another.
Choose by the catalog's stated fit. FLUX Schnell is positioned for fast iteration, Recraft V3 for brand graphics, and FLUX 1.1 Pro Ultra for photoreal detail. For a graphic show mark or abstract editorial symbol, begin with the fast model to test the visual premise. For a design-forward composition, consider Recraft. Use the photoreal option only when photography-like detail is central to the show identity.
Write the prompt for composition, not final lettering
Build the prompt from five controlled parts: show premise, one focal subject or symbol, visual language, restrained palette, and title-safe space. For example: `Investigative technology podcast cover concept; a single luminous circuit forming a question mark; crisp editorial vector-like composition; charcoal, electric blue, and off-white; uncluttered upper third for a short title; no letters, words, logos, badges, or platform marks.`
Requesting no lettering keeps this pass focused on composition. Add the exact show title and host name in a design tool where spelling, font licensing, alignment, and contrast can be verified. Apple recommends making the title clear and prominent, limiting extra text or logos, maintaining contrast, and checking legibility at the different sizes where show covers appear.
A July 2026 r/podcasting thread offers limited, anecdotal workflow evidence rather than a model benchmark: respondents described finishing show art with a designer, Canva, Gimp, Photoshop, Affinity, or Inkscape, and one emphasized simple imagery and large text that survives small-thumbnail display. That discussion supports a downstream human design and thumbnail-review step, but it does not verify this CLI, 1:1 support, model quality, or generation outcomes.
Finish against the podcast-cover delivery contract
Treat the generated square as a concept, then rebuild the final cover at the distributor's required export size. Apple specifies a 3000 by 3000 pixel show cover; RSS submissions may range from 1400 by 1400 to 3000 by 3000, with the largest preferred. It accepts PNG or JPG and requires a solid background without transparency or an alpha channel.
Review at full size and at a small thumbnail. Confirm that the title remains readable, the focal symbol survives reduction, no important element sits near a risky edge, and the final file is sharp. Verify rights for every generated, stock, portrait, logo, and type element before publishing. Apple's policies require rights-cleared artwork and warn that blurry, misaligned, pixelated, or otherwise poor-quality files may be rejected.
- Format
- Square PNG or JPGExport with a solid background and no alpha channel for the Apple show-cover path.
- Size
- 3000 × 3000 preferredDo not upscale a weak concept blindly; rebuild and inspect the final composition at delivery resolution.
- Human gate
- Typography, rights, and thumbnail reviewA person approves exact text, licensing, visual quality, and publication readiness.
Continue with the next narrow review task
Use the MCP workflow directory if you need a different creative asset, the YouTube thumbnail guide when the deliverable is landscape and text-led, and the contact-sheet guide when several controlled podcast-cover directions need side-by-side review. Each route changes the decision being made instead of repeating this square-cover runbook.
Editorial ownership boundary
This page owns the query “cli podcast cover generator” through a square CLI command, a model-fit decision, a podcast-specific prompt, and an export checklist. It does not claim a generated concept is publication-ready or rank image quality. Consolidate it into the creative-workflow directory if current 1:1 support or model-fit evidence can no longer be maintained.