A neutral 2026 reference for Amazon Titan Image Generator on Amazon Bedrock: what it does (text-to-image plus editing — inpainting, outpainting, image variation, background removal, and image conditioning), the built-in invisible watermark that makes every output detectable, how to enable model access and invoke it, the per-image pricing model (billed per generated image by resolution and quality, not per token), how to prompt it well, how it compares to the newer Amazon Nova Canvas and to Stability AI's Stable Diffusion, the use cases it fits, and how AWS credits make the whole pipeline $0.
Amazon Titan Image Generator is the image-generation member of Amazon's first-party Titan family on Amazon Bedrock. It turns a text prompt into an image and, just as importantly, edits existing images — and it is one of several image models you can call through Bedrock's single managed API.
Amazon Bedrock is AWS's fully managed service for calling many foundation models through one API, with enterprise privacy guarantees: your prompts and reference images are not used to train the base models, and they stay inside your AWS account and region. Bedrock hosts models from Anthropic (Claude), Meta (Llama), Mistral, Cohere, Stability AI, AI21, DeepSeek, and Amazon itself. Titan Image Generator is one of Amazon's own image models in that catalog — built, priced, and supported by AWS rather than licensed from a third party — alongside the embedding and text members of the Titan family and the newer Nova family.
Because it lives on Bedrock, Titan Image Generator inherits the platform's posture: the same InvokeModel runtime path, the same IAM permissions, VPC endpoints, KMS encryption, and CloudTrail auditing that govern the rest of your Bedrock usage. You do not provision GPUs, manage capacity, or patch anything — you call a model ID with a request body and receive image bytes. Generated images and the prompts that produced them never leave your account boundary, which is a frequent reason regulated teams generate on Bedrock rather than through a consumer image tool.
There are two generations of the model worth knowing about: the original Titan Image Generator G1 (V1) and the later Titan Image Generator G1 V2, which adds capabilities — most notably image conditioning (guiding generation with a reference image's edges or layout), colour-guided generation, and subject-consistency / background-control features — on top of the V1 editing set. Both are invoked the same way (a JSON body with a taskType); V2 simply exposes more task types and parameters. Names, model IDs, and exact feature availability advance over time, so confirm the current model in the Bedrock model catalog.
The honest framing, stated once up front: Titan Image Generator was Amazon's earlier first-party image model, and Amazon has since shipped Amazon Nova Canvas — the image model in the newer Nova family — which is now Amazon's recommended first-party choice for most new image work. That does not make Titan Image Generator obsolete: it is still available, still low-cost, still carries the invisible watermark, and existing pipelines run on it happily. But if you are starting a new image project in 2026, the realistic first-party comparison is usually Nova Canvas vs a Stability model, with Titan Image Generator the option you keep if it already serves you. This page is honest about that throughout and points to the amazon-nova-canvas sibling where Nova Canvas is the better answer.
Pricing caveat, meant throughout: the figures below are representative as of 2026 to convey relative cost and the shape of a bill. Image-model prices change as AWS ships new models and updates Bedrock, and they vary by region. Confirm current per-image rates on the official AWS Bedrock pricing page before budgeting, and use the amazon-bedrock-pricing-calculator sibling to model your own numbers.
Titan Image Generator = Amazon's first-party text-to-image + editing model on Bedrock, billed per generated image, with an invisible watermark on every output and a detection API. In 2026 it is a capable, low-cost option — but evaluate the newer Amazon Nova Canvas first for fresh image work.
Titan Image Generator covers far more than one-shot generation. Each capability is invoked as a distinct <code>taskType</code> in the request body, which makes the model a small toolkit for the real "generate, then fix" loop that creative and e-commerce work actually need.
The core action is text-to-image: a prompt produces one or more images at a chosen resolution and aspect ratio, with an optional negative prompt (what to exclude) and a seed for reproducibility. Where the model earns its place is the editing operations layered on top — these are the difference between a demo and a production pipeline.
Supply a text prompt and receive a generated image (or a small batch). You control the output through an aspect ratio / explicit dimensions, a negative prompt to steer away from unwanted elements, a seed for reproducible or deliberately varied results, a cfgScale (how strictly the model follows the prompt), and the number of images per request. This is the starting point for most image workloads and the baseline against which the editing task types are measured.
Inpainting changes a masked region of an existing image while keeping the rest intact: remove an object, swap an item, fix a blemish, or replace a logo. You provide the source image, a mask (either a mask image or a maskPrompt describing the region in natural language — e.g. "the coffee cup"), and a prompt for what should appear in the masked area. This is the workhorse for product retouching and targeted edits where regenerating the whole image would be wasteful and inconsistent.
Outpainting extends an image beyond its original frame: widen a scene, change the aspect ratio for a different placement, or add canvas around a subject. As with inpainting you supply the source image and a mask defining what to keep versus generate, plus a prompt describing the new surrounding content. Outpainting is how a single product or hero shot is re-framed into square, portrait, and wide variants for different ad placements without a reshoot.
Image variation takes an existing image (optionally plus a text prompt) and produces alternative versions that preserve the overall content while varying the rendering — useful for generating a set of on-brand options from a reference, or refreshing an asset without starting cold. A similarity-strength control governs how far the variations depart from the source.
Titan Image Generator V2 can remove the background of an image automatically — isolating the subject onto transparency — and, combined with generation, replace what sits behind a subject. For e-commerce this is the high-value operation: take a product photo, strip the background, and place the product into a generated lifestyle scene, at catalog scale, without a studio.
Image conditioning (V2) guides generation with a reference image so the output follows its structure — using a Canny edge reference to preserve outlines and layout, or a segmentation reference to preserve the arrangement of regions — while the prompt dictates the content and style. Colour-guided generation conditions the output on a supplied palette (a list of hex colours), which is how you keep generated assets on a brand's exact colours. Subject consistency and background-control features help keep the same subject across multiple generations.
Text-to-image · inpainting · outpainting · image variation · background removal/replacement · image conditioning (Canny/segmentation) · colour-guided generation · subject consistency. Each is a taskType in the request body — so a "generate then edit" pipeline is a sequence of Bedrock calls, not separate tools.
A distinguishing feature of Amazon's own image models is provenance: every image Titan Image Generator produces carries a built-in, imperceptible watermark, and Bedrock gives you an API to detect it. As AI-generated media becomes regulated, this is a feature buyers increasingly require rather than a nice-to-have.
The invisible watermark is applied automatically to every generated image — there is no flag to turn it on, and it does not visibly alter the picture. It is designed to survive common transformations (resizing, compression, modest cropping) better than a visible overlay would, so the provenance signal persists through a normal asset pipeline. This is distinct from a visible "made with AI" badge; the point is a durable, machine-detectable marker of origin.
Bedrock exposes a watermark-detection capability (the DetectGeneratedContent / image-watermark-detection API): you submit an image and Bedrock reports whether it carries an Amazon-generated watermark, typically with a confidence indication. That lets you build content-authenticity checks into your own systems — for example, verifying whether an uploaded asset was produced by your Titan pipeline, or screening user uploads. The detection covers images generated by Amazon's own models (Titan Image Generator and Nova Canvas).
Why this matters: regulators and platforms are moving toward disclosure and provenance requirements for synthetic media, and industry standards such as C2PA content credentials are gaining adoption. Titan Image Generator's built-in watermark is one concrete answer to "can you prove this image was AI-generated, and that it came from your system?" — a question that does not arise with most third-party image models, which do not watermark by default. If disclosure or provenance is part of your compliance posture (regulated advertising, news, marketplaces with AI-content policies), the built-in watermark is a reason to weight Amazon's image models over alternatives.
Every Titan Image Generator output is invisibly watermarked by default, and Bedrock can detect it via API. Stability AI's models do not watermark by default; Amazon's own models (Titan Image Generator and Nova Canvas) do. If provenance / disclosure is a compliance requirement, that tilts the choice toward the Amazon models.
Foundation models are off by default on Bedrock. Getting from zero to a generated image is a short, well-trodden path: request model access, get the current model ID, then call InvokeModel with a task-specific JSON body. Enabling access is free — you pay only when you generate an image.
Enabling access. In the Bedrock console open Model access, find Amazon Titan Image Generator (G1 and/or G1 V2), and request access. First-party Amazon models are typically granted effectively immediately. Access is per-account and per-region, so enable it in each region you will call from. Image-model regional availability is narrower than the big text models, so confirm the exact model is offered in your chosen region before designing around it.
Model IDs. Every Bedrock model is invoked by a model ID — a string identifying provider, model, and version, namespaced under Amazon (of the shape amazon.titan-image-generator-… with a version suffix such as v1 or v2). Read the current ID from the Bedrock model catalog or list it via the API/CLI; treat it as configuration rather than a hard-coded literal, because IDs advance as new versions ship.
Invoking. Image generation uses Bedrock's InvokeModel action with a model-specific JSON body — the model-agnostic Converse API is for conversational text/multimodal models, not image generation. The body is organized around a taskType: TEXT_IMAGE for text-to-image, INPAINTING, OUTPAINTING, IMAGE_VARIATION, BACKGROUND_REMOVAL, COLOR_GUIDED_GENERATION, and the conditioning task types in V2. Alongside the task block you pass an imageGenerationConfig (number of images, resolution/dimensions, cfgScale, and a seed). The response returns the generated image(s) as base64-encoded bytes that you decode and store. SDKs exist for Python (boto3), JavaScript, Java, and more.
Permissions. The IAM principal making the call needs permission for the Bedrock invoke action on the specific Titan Image Generator model ARNs. A least-privilege policy scoped to the model IDs you intend to use is the recommended posture — and the same VPC endpoint, KMS, and CloudTrail controls that govern the rest of your Bedrock usage apply, so generated images and prompts stay inside your account and region.
taskType body (TEXT_IMAGE / INPAINTING / OUTPAINTING / IMAGE_VARIATION / BACKGROUND_REMOVAL / …) plus an imageGenerationConfig; decode the base64 image from the response.Titan Image Generator is billed per generated image, not per token. The rate depends on the output resolution and the quality setting (standard vs premium), and editing operations (inpainting, outpainting, variation, background removal) bill per output image just like fresh generation.
This is the structural difference from the text models elsewhere in this cluster: there is no per-1K-token meter and no prompt caching — the unit of cost is one finished image. The price scales with resolution (a larger image costs more than a smaller one) and with the quality tier (a premium-quality image costs more than a standard-quality one). Generating N images per request bills N images, so the number of candidates you produce per prompt is a real cost lever. Editing task types are billed the same per-output way — an inpaint that returns one image costs one image.
The table below gives representative 2026 per-image figures to rank the tiers and sanity-check a budget — treat them as orders of magnitude, not an audited price sheet, because Bedrock prices change and vary by region. The dominant levers for an image workload are different from a text one: resolution, quality tier, and candidates per prompt — not context length or caching. A practical pattern is to generate cheap standard-quality drafts, pick the winner, then re-render only that one at premium quality and higher resolution.
| Output | Quality | Representative price / image | Relative cost | Notes |
|---|---|---|---|---|
| Up to 1024×1024 | Standard | ~$0.008 | Lowest | Default workhorse size for drafts and most web assets |
| Up to 1024×1024 | Premium | ~$0.01 | Low | Higher fidelity for the same dimensions; finals |
| Larger than 1024×1024 | Standard | ~$0.01 | Low–mid | Bigger images cost more per image |
| Larger than 1024×1024 | Premium | ~$0.012 | Mid | Highest fidelity at larger sizes; hero assets |
| Editing (inpaint/outpaint/variation/bg-removal) | Std / Premium | Billed per output image | Same as generation | Each returned image bills like a fresh generation |
Good image output is mostly good prompting plus the right control parameters. Titan Image Generator rewards clear, descriptive prompts and a small set of levers — negative prompt, seed, cfgScale, and resolution — used deliberately rather than stuffed.
Describe the image as a clear scene: state the subject, the setting, the composition and framing (close-up, wide, overhead), the lighting (soft daylight, studio softbox, dramatic rim light), the style or medium (photograph, 3D render, illustration), and any mood or colour direction. Specificity beats length — a precise, well-ordered description outperforms a long pile of adjectives. Use the negative prompt to subtract unwanted elements rather than to add new ones.
A reliable pattern: [subject] + [key details] + [setting] + [composition/framing] + [lighting] + [style/medium] + [mood/colour], written as a clear sentence — plus a focused negative prompt (positively phrased) for clean-up and a pinned seed when you need consistency. Specific and well-ordered beats long and vague.
Titan Image Generator is one of several image options on Bedrock. The two others people weigh it against are Amazon's own newer Nova Canvas and Stability AI's Stable Diffusion / Stable Image line. A neutral orientation — they overlap, and the right pick is workload-specific.
Titan Image Generator vs Amazon Nova Canvas. Nova Canvas is Amazon's newer first-party image model (part of the Nova family) and covers a similar surface — text-to-image, inpainting, outpainting, image variation, background removal — also with an invisible watermark on every image and built-in content controls. As Amazon's current image model it is the one to evaluate first for new work; it generally benefits from the more recent training and feature set. Titan Image Generator remains a capable, low-cost option and is the sensible choice if you already run it or want its specific behaviour, but for a fresh pipeline the honest default is to start with Nova Canvas and only stay on Titan if it wins your eval. See the amazon-nova-canvas sibling.
Titan Image Generator vs Stability AI (Stable Diffusion / Stable Image). Stability's models on Bedrock — the SDXL-era Stable Diffusion plus the newer Stable Image line (Core, Stable Diffusion 3.x, Stable Image Ultra) — are the strong third-party alternative. Stability tends to win when you want its particular aesthetic, the breadth of the Stable Diffusion style vocabulary, the SDXL-era model's fine-grained step/cfg control, or the top-end photorealism of Stable Image Ultra. Titan Image Generator's counter-advantages are first-party convenience, low per-image cost, and the built-in invisible watermark (Stability does not watermark by default) — which matters when provenance is a requirement. See the stable-diffusion-on-amazon-bedrock and ai-image-generation-on-aws siblings.
The meta-point holds across Bedrock: every image model sits behind the same account, IAM, VPC, billing, and credit setup, so you can enable several, A/B them on your own prompts and brand, and route per use case — Titan Image Generator or Nova Canvas where the built-in watermark and first-party editing fit, a Stability model where you want its aesthetic or Ultra-tier photorealism — without re-plumbing anything. Benchmark on your imagery rather than on sample galleries, since relative quality shifts with each model generation.
Cutting through the marketing, here are the concrete situations where reaching for Titan Image Generator is a sound call today — and where the editing task types, not raw generation, are the reason.
The through-line: Titan Image Generator's sweet spot is editing-heavy, provenance-sensitive, first-party image work — product imagery, marketing assets, and any existing pipeline already built on it. For brand-new generation where you want maximum quality, evaluate Nova Canvas (newer) and Stability (aesthetic / Ultra) too. Use this list to place your workload.
Everything above prices Titan Image Generator if you pay AWS directly. For most startups and many companies the relevant number is different — because AWS will frequently fund the build with credits, and per-image generation on Bedrock draws those credits down before it ever touches your card.
Image generation on Bedrock is ordinary AWS spend, so it is fully credit-eligible and credits apply automatically against your bill until exhausted — covering every generated image plus the supporting services (S3 for storing generated assets, Lambda or containers for the generation pipeline, a CDN for delivery, and logging). The relevant pools: AWS Activate (general startup credits, commonly up to $100K for institutionally-funded startups); a dedicated Bedrock / Generative-AI POC pool ($10K–$50K) aimed at proving out a GenAI use case — an image pipeline is a textbook fit; and the competitive Generative AI Accelerator (awards up to $1M for a small cohort of AI-first startups). Because generation is billed per image, a credit pool maps directly onto a budget you can reason about: at low-cents-per-image, a $25K POC pool is, very roughly, millions of standard images.
The practical mechanic is that most of these pools are partner-filed — requested through the AWS Partner Network (the ACE program), not a public self-serve form — which is why teams route through an AWS partner rather than applying alone. That is the gap CloudRoute fills. CloudRoute matches you to the right credit pool for your stage and to a vetted AWS DevOps/ML partner who both files the credit application and helps build the image workload — the generation and editing calls behind a queue, the draft-at-standard / finish-at-premium routing, background-removal and inpainting endpoints, asset storage and delivery, watermark-detection checks, and a moderation layer for user-facing generation. The customer pays $0 — AWS funds the credit pool, AWS pays the partner through engagement-funding programs, and the partner pays CloudRoute a routing commission. You never see an invoice from us.
Put together with the per-image levers above, the picture for a startup is: draft cheaply, finish premium, store and deliver on AWS, prove provenance with the built-in watermark, and run the whole pipeline on a $25K–$100K (or larger) credit pool while you find product-market fit — paying real money only once generation volume, and ideally revenue, has scaled past the credits. Related: the cross-cluster pages on $100K AWS credits, AWS credits for generative-AI startups, and Bedrock POC funding for the full credit mechanics.
Get AWS credits to run Titan Image Generator (and Nova Canvas, Stable Diffusion, and the rest) on Bedrock — and get connected to a vetted AWS partner who builds the image pipeline for you. AWS funds it; the partner pays CloudRoute; you pay $0.
The image-model decision in one place: Amazon's Titan Image Generator against its newer Nova Canvas and Stability AI's line, compared on provider, billing, editing, watermarking, and the work each suits. Representative 2026 figures for relative comparison, not quotes — benchmark on your own brand imagery.
| Model | Provider | Billing | Editing (inpaint/outpaint/bg) | Invisible watermark | Best for |
|---|---|---|---|---|---|
| Amazon Titan Image Generator | Amazon (first-party) | Per image (by resolution × quality, ~$0.008–$0.012) | Built-in (inpaint, outpaint, variation, bg removal, conditioning) | Yes (every image) | Low-cost first-party editing + provenance; existing pipelines |
| Amazon Nova Canvas | Amazon (first-party, newer) | Per image (by resolution/quality) | Built-in (inpaint, outpaint, variation, bg removal) | Yes (every image) | New first-party image work — evaluate this first |
| Stable Image Core | Stability AI | Per image (~$0.04, flat) | Via edit endpoints | No (by default) | High-volume drafts, fast iteration |
| Stable Diffusion 3.x | Stability AI | Per image (~$0.06–$0.08, flat) | Via edit endpoints | No (by default) | Strong general default; prompt adherence, in-image text |
| Stable Image Ultra | Stability AI | Per image (~$0.12–$0.14, flat) | Via edit endpoints | No (by default) | Hero images, photorealism, final assets |
Situation: Sellers uploaded inconsistent product photos — mixed backgrounds, mixed aspect ratios — and the team needed clean, on-brand catalog and ad imagery at scale without a studio or a per-seat consumer tool. They also had a compliance requirement to be able to prove which catalog images were AI-generated. They were already on AWS for the marketplace and wanted GenAI POC funding to de-risk the build.
What CloudRoute did: CloudRoute matched them in under 24 hours to a UAE/EU AWS partner with a Bedrock GenAI track record. The partner built a pipeline on Titan Image Generator V2: background removal to isolate each product, generation to place it into on-brand lifestyle scenes, outpainting to re-frame each asset into square / portrait / wide placements, and colour-guided generation to hold the brand palette — drafts at standard quality, finals at premium. They wired Bedrock's watermark-detection check into the asset-ingest path for the provenance requirement, stored and delivered via S3 + CloudFront, and added a moderation step. They filed a Bedrock/GenAI POC credit request plus Activate so the build and early generation were credit-funded.
Outcome: The marketplace now produces consistent catalog and ad imagery on its own AWS account — background-stripped, scene-placed, re-framed per placement — with every generated image drawing down AWS credits instead of seed runway, so the team pays $0 during the build and early scale. The draft-at-standard / finish-at-premium split kept per-asset cost in the low cents, and the built-in watermark plus detection satisfied the provenance requirement out of the box. CloudRoute's commission was paid by the partner from AWS engagement funding — the customer paid $0.
pipeline: bg-removal → scene generation → outpaint re-frame + colour-guided · provenance: built-in watermark + detection · credits secured: POC + Activate · out-of-pocket: $0
Image generation on Bedrock is billed per image — and every image Titan generates draws down AWS credits, under your existing IAM, VPC, and billing, with a built-in watermark for provenance. CloudRoute routes you to the right credit pool (Activate up to $100K, Bedrock POC $10K–$50K, GenAI Accelerator up to $1M) and a vetted AWS partner who builds the Titan Image Generator pipeline — background removal, scene generation, outpaint re-framing, draft-at-standard / finish-at-premium. Customer pays $0.