von OpenAIBild

GPT Image

12 Modelle · ab 30 Credits

Modelle der Familie GPT Image

ModellModusPreisSeitenverhältnisse
GPT Image 1.5 EditBildbearbeitungab 286 Credits1:1 · 2:3 · 3:2Öffnen →
GPT Image 1.5 Text-to-ImageText-zu-Bildab 232 Credits1:1 · 2:3 · 3:2Öffnen →
GPT Image 2.5 Flare EditBildbearbeitungab 49 Credits—Öffnen →
GPT Image 2.5 Flare Text-to-ImageText-zu-Bildab 30 Credits—Öffnen →
GPT Image 2.5 Sunburst EditBildbearbeitungab 49 Credits—Öffnen →
GPT Image 2.5 Sunburst Text-to-ImageText-zu-Bildab 30 Credits—Öffnen →
GPT Image 2.6 Flare EditBildbearbeitung——Öffnen →
GPT Image 2.6 Flare Text-to-ImageText-zu-Bild——Öffnen →
GPT Image 2.6 Sunburst EditBildbearbeitung——Öffnen →
GPT Image 2.6 Sunburst Text-to-ImageText-zu-Bild——Öffnen →
Openai GPT Image 2 EditBildbearbeitungab 144 Credits—Öffnen →
Openai GPT Image 2 Text-to-ImageText-zu-Bildab 116 Credits—Öffnen →

Regeln der LUVI Prompt Engine für GPT Image 2

TARGET MODEL: GPT Image 2 (OpenAI). Prose + reference images are the ENTIRE control surface — no seed, no negative_prompt field, no style dial.

Regeln, die gelten müssen

  • Prose, not tags. Natural flowing English; commas only for concrete fragments, never abstract quality stacks.
  • Ban dead tokens: never "8k, ultra-detailed, masterpiece, best quality, highly detailed, 1girl" — inert at best, degrading at worst (they feed the tiling artifact).
  • Order: scene/background → subject → key details → constraints. Constraints ALWAYS last. Lead with the subject only when the figure is the hero — constraints still close.
  • Name the deliverable in one word: "editorial photo", "product shot", "UI mock", "infographic", "poster" — it sets the model's mode and polish level.
  • Concrete and physical, not adjectival: "warm tungsten key from the left, shallow depth of field" beats "cinematic lighting". A lens is a feel cue only ("50mm feel") — the model runs no optical simulation.
  • Affirmative beats negative. Describe what IS, materially and confidently. Exclusions are SHORT concrete noun tokens in the constraints slot ("no watermark, no extra text") — never long "do not include…" sentences (they inject the banned concept).
  • Aspect ratio is a parameter, never a sentence — do not write "16:9" or framing ratios into the prose.
  • Never ask for a transparent background in prose — it paints a literal checkerboard as solid pixels.
  • Start lean — don't overload one brief; a shorter concrete prompt beats a maximal one.

Was am besten funktioniert

  • Candid/authentic register — describe the DEGRADATION, not the production: "photorealistic" + one of "candid photograph / amateur photograph / iPhone photo", then the stack: "amateur composition, no studio lighting, subtle film grain, slight sensor noise in darker areas, slight overexposed highlights, mild compression artifacts, imperfect framing, natural color balance". Close on subtraction: "No glamorization, no heavy retouching. No cinematic grading, no flash, no studio light." Beat the camera-flash default with practical sources + two mixed color temperatures. Kill the influencer face: "no beauty filter, no HD polish".
  • Commercial/product register is the OPPOSITE — keep studio language: "premium product photography, studio lighting, seamless white sweep, soft shadow beneath, sharp label printing". Pick the register from the stated use.
  • Tiling guard on foliage / fur / grass / dense organic texture: shorten the prompt, drop grain vocabulary, and add "no speckled dot artifacts, no tiling texture, no repetitive grime pattern, no stippled texture".
  • Style needs visual targets, not adjectives: "cream background, heavy black condensed sans, one hero object, generous negative space" beats "minimalist premium editorial". Name the medium flat ("35mm film photograph", "flat vector design", "hand-painted watercolor"); hyper-specific device/era mediums land ("early 2000s CCTV security camera", "low-poly PlayStation screengrab").
  • Fight the warm/yellow house cast with explicit "natural color balance".
  • In-image text: quote the literal copy in "double quotes" or ALL CAPS; describe type as a separate spatial constraint (weight, color, placement); spell tricky or brand words letter-by-letter; keep each text zone to 5 words or fewer and bind distinct strings to distinct objects ("Include ONLY this label text (verbatim): …"); multiple text blocks in one frame MERGE — keep blocks few; fence phantom text every time: "No other visible words. No random letters. No duplicate text. No watermark." and assert the single instance ("Render the tagline exactly once.").
  • Character consistency is prompt-only — restate the preserve-list every turn ("change only X, keep everything else the same") and enumerate the identity traits; pair PRESERVE attributes with EXCLUDE additions ("no text, no watermark, no logos"). One change per edit.

Aus den Regeln der LUVI Prompt Engine für diese Familie; dieselben Regeln wenden der Rewriter im Arbeitsbereich und LUVIs MCP-Connector an.

Regeln der LUVI Prompt Engine für GPT Image 2.5

TARGET MODEL: GPT Image 2.5 (OpenAI — Flare and Sunburst read the same dialect). The prompt reaches the model exactly as written. Prose, reference images and the app's settings (size, quality, background) are the whole control surface — there is no seed, no negative_prompt field, no weighting and no special token syntax.

Regeln, die gelten müssen

  • Keep the user's subject, intent and every quoted string exactly. Reshape; do not invent. Never add props, scene elements, people, wardrobe, architecture, materials, weather, time of day, light, lenses, styles or orientation words ("vertical", "wide") the user did not give — this model already fills empty scenes with extras on its own. A short brief stays short: "a red vespa in a narrow Istanbul street" must NOT gain cobblestones, shuttered windows or afternoon light.
  • Every format works on this model (prose, tags, JSON-like, labeled sections). If you restructure a JSON-like or tag prompt, carry over every value — no field may be dropped or reinterpreted.
  • Name the deliverable and its use in the opening words: "a vertical retail poster for a coffee roastery", "a product photograph for a web shop", "an infographic for high-school students".
  • In-image text: every visible string in double quotes, exactly as it must read, with its position and typography in plain words; say "exactly once" when repetition would hurt. Keep non-English characters exact (Turkish İ ı ş ğ ç ö ü, ₺). A name given only as context ("a roastery called X") is not printed — when the deliverable obviously carries it (packaging, label, logo, sign, storefront, poster for that brand), quote the name and say where it is printed: a jar label reading "Arı Bal".
  • End with the exclusions the result needs, as short plain negatives — they are safe and obeyed on this model: "No other text." · "No watermark, no logos." When the scene invites lettering the user did not ask for (a named town, harbor, street, shopfront, vehicle), add "No text, signs or lettering anywhere."
  • Transparent background: the app's background=transparent setting makes the alpha; the words alone paint a fake checkerboard. When the user wants a cutout, describe ONE isolated subject with nothing behind it (no backdrop, floor, scene or colour) and add "Fully transparent background, no checkerboard, no shadow plate."
  • Aspect ratio and resolution are settings. Do not write ratio numbers ("16:9") or resolutions ("4K", "8k") into the prompt; describe the composition in words instead ("a wide landscape", "a tall vertical poster with empty space at the top for the headline").

Was am besten funktioniert

  • For a long brief use the order scene → subject → details → constraints; labeled sections ("Scene:", "Subject:", "Style:", "Text:", "Constraints:") are fine.
  • Describe what is visible: materials, light, colour, medium, framing, texture. Ask for "photorealistic" or "real photograph" only when realism is the goal; camera terms ("35mm film photograph, eye level, 50mm lens") are look cues, not physics.
  • Replace mood words and quality boosters ("cinematic", "stunning", "8k, masterpiece, best quality") with scale, atmosphere, colour and concrete detail.
  • Candid or authentic photos: "It should look like a real photograph someone could have taken, not an overly enhanced or cinematic image. No glamorization, no heavy retouching."
  • People: body framing, relative scale, gaze and what the hands do ("full body visible, feet included", "looking down at the open book").
  • Charts, slides, diagrams: put the real numbers and labels into the prompt.

Aus den Regeln der LUVI Prompt Engine für diese Familie; dieselben Regeln wenden der Rewriter im Arbeitsbereich und LUVIs MCP-Connector an.

Regeln der LUVI Prompt Engine für GPT Image 2.6

TARGET MODEL: GPT Image 2.6 (OpenAI — Flare and Sunburst read the same dialect). The prompt reaches the model exactly as written. Prose, reference images and the app's settings (size, quality, complexity, background) are the whole control surface — there is no seed, no negative_prompt field, no weighting and no special token syntax.

Regeln, die gelten müssen

  • Keep the user's subject, intent and every quoted string exactly, and every style or medium word they gave, in English when you translate ("fotoğraf gerçekçi" → "Photorealistic photograph.", "yağlı boya" → "oil painting", "3D render", "watercolour") — dropping one changes the look of the result. Reshape; do not invent. Never add props, scene elements, people, wardrobe, architecture, materials, weather, time of day, light, lenses, styles or orientation words ("vertical", "wide") the user did not give. A short brief stays short: "a red vespa in a narrow Istanbul street" must NOT gain cobblestones, shuttered windows or afternoon light — and do not restate the brief in a second sentence.
  • Every format works on this model (short prompts, prose, tags, JSON-like, labeled sections). If you restructure a JSON-like or tag prompt, carry over every value — no field may be dropped or reinterpreted.
  • Name the deliverable and its use in the opening words when the user gave them: "a vertical retail poster for a coffee roastery", "a product photograph for a web shop", "an infographic for high-school students".
  • In-image text: every visible string in double quotes, exactly as it must read, with its position and typography in plain words; say how many times it appears when repetition would hurt ("exactly once"). A string the user put in quotes — single quotes, typographic quotes or double quotes — is written in double quotes in your output, letter for letter: 'Bayramınız Kutlu Olsun' becomes "Bayramınız Kutlu Olsun". Never turn quoted copy into plain words. Keep non-English characters exact (Turkish İ ı ş ğ ç ö ü, ₺). Spell an unusual brand name letter by letter only if the user did.
  • A name the user gives for a product, shop or brand is printed by this model whenever the image has room for it, and it invents label copy around it (live: "a coffee bag from a roastery called Kuzey Kavurma" came back with "Kuzey Kavurma" plus an invented origin, tasting notes and weight). So when the image shows the thing that carries the name — the brand's packaging, label, bottle, sign, storefront, logo, menu or poster — always add one sentence that quotes the name and says where it is printed, then end with "No other text.": "… on a wooden shelf. The bag's label reads "Kuzey Kavurma". No other text." (live: only the name, no invented copy, 2/2). Copy the user gave beside the name (a slogan, a price, a line) is quoted in the same sentence with its place, and the name stays in it: "The can reads "<name>" and, below it, "<slogan>"." A name that only describes a person or place in the scene ("a barista who works at a café called Moka") gets no such sentence.
  • Exclusions are short plain sentences at the end: "No other text." · "No watermark, no logos." Keep every exclusion the user wrote. When the image carries quoted text, end with "No other text." (OpenAI's guide asks for no extra text around required copy; live, it removed invented lettering).
  • When the user says the image should carry no text (in any words: "no text", "without text", "yazısız", "yazı olmasın") and the scene invites lettering — a town, street, harbor, market, shopfront, café, station or vehicle — write that exclusion as "No text, signs or lettering anywhere." (live: a plain street scene came back with a chalkboard menu and a flag; with this sentence, none). When the user said nothing about text, add no text exclusion: signs in a street are part of the scene. Add no other exclusion of your own.
  • Transparent background is a setting (background=transparent, PNG). When the user wants a cutout, describe ONE isolated subject with nothing behind it — no backdrop, floor, scene or colour — and keep any "transparent background" words the user wrote.
  • Aspect ratio, resolution, quality and complexity are settings. Do not write ratio numbers ("16:9"), resolutions ("4K", "8k") or "low/high complexity" into the prompt; describe the composition in words instead ("a wide landscape", "a tall vertical poster with empty space at the top for the headline").

Was am besten funktioniert

  • For a long brief use the order scene → subject → details → constraints; labeled sections ("Scene:", "Subject:", "Details:", "Text:", "Constraints:") are fine.
  • Describe what is visible: materials, light, colour, medium, framing, texture. Ask for "photorealistic" or "real photograph" only when realism is the user's goal; camera terms ("35mm film photograph, eye level, 50mm lens") are look cues, not physics.
  • Replace mood words and quality boosters ("cinematic", "stunning", "8k, masterpiece, best quality") with the scale, atmosphere, colour and concrete detail the user already gave — never with new content.
  • People: body framing, relative scale, gaze and what the hands do ("full body visible, feet included", "looking down at the open book"), when the user described the person.
  • Charts, slides, diagrams: keep the real numbers and labels in the prompt.

Aus den Regeln der LUVI Prompt Engine für diese Familie; dieselben Regeln wenden der Rewriter im Arbeitsbereich und LUVIs MCP-Connector an.