
Use 1K previews before 4K final image generations when screening many ideas and approving only a smaller subset for final work. At current Imagild rates, one 1K preview costs 10 points and one new 4K generation costs 20. An approved preview followed by a final therefore uses 30 points, not a discounted twenty-point upgrade.
This workflow can reduce the total cost of rejected concepts. It does not guarantee lower spending for every acceptance rate, identical composition across generations, or a hidden upscale operation.
Key Takeaways
- Budget previews and final generations as separate tasks with separate identities.
- Compare
10 × concepts + 20 × approved finalswith generating every concept at 4K. - Inspect each final again; a good preview does not establish an acceptable final image.
Write the comparison before choosing a workflow
Let N be the number of ideas you preview once at 1K, and A the number that receive one new 4K generation. Assume every listed generation succeeds and there are no further retakes.
preview-first plan = 10N + 20A points
all-4K plan = 20N points
preview-first uses fewer points when A < N / 2
For twenty concepts:
| Concepts previewed | Approved for 4K | Preview-first points | All twenty at 4K |
|---|---|---|---|
| 20 | 5 | 300 | 400 |
| 20 | 10 | 400 | 400 |
| 20 | 15 | 500 | 400 |
At five approvals, screening saves 100 points in this simplified comparison. At fifteen, it costs an extra 100. These are planning calculations, not measured customer acceptance rates or a claim about a competitor's prices.
Use the current model hub to confirm 1K and 4K rates before applying this calculation.
Decide what a preview is allowed to prove
A preview can help reject a weak direction, wrong object arrangement, unsuitable color palette or poor framing. It cannot prove that a later generation will preserve exact lettering, faces or product details.
Write a short acceptance brief before the preview stage: intended subject, composition, visible text requirements and protected details. Approve the direction rather than promising the smaller file is a deterministic blueprint.
The reference-scope guide helps describe whether a final should borrow an object or preserve a whole scene.
Make the final an explicit new operation
After approval, construct a new image request with a supported model and resolution: "4K". Give it a new Idempotency-Key because it is a new generation. Retrying an interrupted preview retains the preview's original key; it does not become the final.
You can use a successful, available image task owned by the same account as image_task_id when the final should reference that preview. Send one reference selector and a meaningful edit instruction; referenced image prompts require at least twenty characters.
This is reference-guided generation, not an API endpoint that simply enlarges the same pixels. Do not add unsupported image parameters such as size, seed or an invented upscale flag. The API console defines the actual fields.
Include the costs the simple table leaves out
Repeated preview attempts, multiple finals, separately generated source images and creative retakes all add to the total. Membership eligibility is required separately, and pack cash purchases, taxes and checkout terms need their own accounting treatment.
Runware's pricing documentation also distinguishes generation configurations when explaining costs. Its pricing options and payment features are not Imagild controls.
Do not advertise “preview first always saves money.” State your actual concept count and approval assumption so the customer can decide whether screening fits the project.
Verify the final delivery independently
Persist preview and final task IDs in separate application rows, linked by your approval record. After the final succeeds, download the actual file and check dimensions, spelling, subject details and intended crop.
Confirm that the invoice view shows the 10-point preview and 20-point final rather than silently replacing the earlier task's quote. The points planning guide supplies broader budget context. A transparent two-stage workflow gives users control over concept screening without disguising additional generation as a free upgrade.
Related tasks
- Should an AI Reference Replace an Object or Bring in the Whole Scene?
- Imagild Points, Resolution and Jobs: Plan a Creation Before You Spend
Sources and scope
- Imagild API console: Current active-member access, generation contract and per-task usage fields, independently cross-checked in lib/relay and claims.json dated 2026-10-28.
- Imagild model hub: Current image 10/15/20-point tiers, H3 duration/resolution rates and five-point enhancement option; not a quality or comparative availability benchmark.
- Runware Pricing: General distinction between configuration-based generation pricing, per-request cost and account payment management. Runware-specific fields, features and policies are not attributed to Imagild.
Product instructions were checked against the current Imagild API contract and the public model catalog. Code, budgets and acceptance checks are illustrative; this article does not claim a new paid generation test, an uptime measurement, a search-volume study or a ranking of AI citations.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: Original Imagild product screenshot captured on 28 October 2026; model availability and prices may change. This image is not an API response or a performance benchmark.