FAQ

Aurivis is built for ecommerce sellers, operators, brand teams, and agencies that need product images, ad creatives, banners, social visuals, and detail-page assets quickly.

No. Start from a workflow or template, then describe the product in plain language: what it is, its color, material, target channel, and the kind of image you need.

A clear source image works best: full product visible, clean edges, even lighting, and a simple background. If the upload is blurry, overexposed, cropped badly, or blocked by props, the result is more likely to drift.

Yes. Aurivis can help you create draft white-background main images and product variants for ecommerce. Before publishing, you should still manually review platform-specific rules for background, shadows, borders, text, and composition.

Yes. It works well for selling-point graphics, material closeups, size visuals, and supporting detail-page images. For more stable output, generate one module at a time instead of asking for a full long layout in one shot.

Yes. One source image can expand into ad creatives, storefront banners, social posts, and campaign visuals. The most reliable workflow is to keep the same source image and change the usage goal by channel.

Yes. You can generate a batch, compare directions, then continue refining the strongest result. In practice, it is usually faster to pick the best direction first than to try to force one perfect image on the first run.

Image generation is probabilistic, so repeated runs can vary. To make results more stable, keep the same source image, model, ratio, and core prompt, and avoid very long or conflicting instructions.

Upload a cleaner source image and explicitly ask to preserve color, material, silhouette, and print placement. If you add too many scene changes or styling demands, the model is more likely to sacrifice product accuracy.

That is a common limitation of image models, especially for small text, exact brand marks, and rigid layout. A more reliable workflow is to generate the base visual first, then add text and logos afterward in a design tool.

Yes. Aurivis also supports fashion-oriented workflows such as model images and try-on style results. For better output, the clothing source image should be front-facing, clear, and show the garment shape completely.

Use Agnes for low-friction free testing, Seedream for general ecommerce visuals, GPT-Img-2-Ultra when you want stronger commercial polish and detail, and Nano Banana models when reference-based editing matters more than pure generation.

Some Agnes workflows are available as lightweight free entry points, but most saved projects, paid models, and higher-credit operations still require login. If you want to manage projects, continue editing, or buy credits, logging in is the safer default.

Credit use mainly depends on model choice, resolution, image count, and edit type. Check the estimate before generating so you do not accidentally run a heavier setup than you need.

The current run will stop and the product will prompt you to log in, recharge, or switch to a lighter workflow. If you are still testing direction, using fewer images and a lower-cost model is usually more efficient.

Yes, Aurivis is suitable for draft visuals, testing, and final candidate images for those channels. You should still manually review each platform's rules before publishing, especially around white backgrounds, collages, text, borders, and image size.

Paid newly generated images are intended for commercial use and do not carry the site watermark. You are still responsible for checking product truthfulness, rights, trademark risk, and marketplace or ad-policy compliance.

Start with the basics: file format, file clarity, network status, login state, remaining credits, and whether the prompt is too long. A clearer PNG, JPG, or WebP source and a shorter prompt usually improve recovery.

Yes. After generation, you can keep refining the strongest result with follow-up edits such as background removal, outpainting, erase, or upscale. A good workflow is to choose the closest result first, then edit from there instead of restarting from zero.

Right now the core product is still a web tool focused on upload, generate, edit, and download. For sellers and agency teams, it already works as a practical production layer for product and campaign visuals, while deeper platform sync can come later.