Use ArchScene with fewer questions and more control.

This guide is for product users, not developers. It walks through uploads, SKP, credits, privacy, current limitations, and how to ask for help.

Open my workbench Report a problem

1. Upload images or scenes

Send technical project images or extract SKP scenes when they're available.

2. Render in batches

Pick what goes to the gallery and send it to the AI with credits in plain sight.

3. Compare and select

Review results, failures, and credits before moving to client delivery.

FAQ

Questions that save you rework.

If something falls outside this guide, send it through support. That helps us tell real bugs apart from expected AI behavior.

Which images should I send?

PNG, JPG, and WebP work best. Use clean exports, good resolution, no important crops, and a final composition you've already locked in.

Does an SKP upload cost credits?

Reading an SKP file identifies scenes and thumbnails. It doesn't call any AI and doesn't consume credits. The actual generation happens later, when you send images or scenes to render.

When does a credit come back?

Credits are reserved before the AI call. A completed render consumes the credit. Technical failures can trigger an automatic refund. A successful but disappointing result should be reported for review.

Are my files private?

Source files, scenes, and results stay private to your account. Don't share screenshots with cookies, signed URLs, or sensitive data when contacting support.

What are the current limits?

At this stage you may see fidelity variations, queue delays, model failures, incomplete thumbnails, or differences between expected and generated materials.

How do I report a problem?

Use the support page and include the project, image, or job when possible. The app attaches only safe context, never private files, cookies, or keys.

Quick fixes

Upload failed: confirm the format and size, then resubmit the file.
Render failed: check the render queue and use Report a problem on the job.
Credit not refunded: technical failures should appear as refunds in the queue.
Missing result: check the gallery and project view; renders stay tied to the original image.
SKP without scenes: confirm the file actually has scenes saved in SketchUp.

Known limitations

AI may vary materials, lighting, and small details between attempts.
SKP scenes still need manual confirmation before joining the gallery.
AI Auditor and full billing remain controlled flows while the product matures.
The queue helps track jobs, but some processing may still need manual follow-up.

Privacy

Source files and results are private by default. Support only stores safe context: user, route, project or job when provided, timestamp, and browser.

Localized quick guide

Quick reference for the team.

How it works

Upload project images or SKP scenes, save selected items to the gallery, render in batches, compare results, and keep the best version.

Credits and refunds

Credits are reserved before AI rendering. Completed renders consume credits. Technical failures can be refunded automatically.

Privacy

Source files and generated renders are private by default. Don't send cookies, API keys, signed URLs, or private files in support messages.

Current limits

Model fidelity, queue delays, render variation, and SKP preview limits can still happen while the product evolves.