KuunAI Documentation
Product guidance for understanding the platform, installing the SketchUp plugin, configuring Studio, using Detail Ops, and managing renders inside Archive.
What is KuunAI
Explains which problem KuunAI solves, which bridge is available today, and the core gains it creates for users.
SketchUp
SketchUp is currently the only live workflow. This section combines plugin installation with the detailed KuunAI usage guide.
Plan details and payments
Collects the main commercial information users need about subscriptions, extra credits, and the payment flow.
Frequently asked questions
Official answers to the questions KuunAI users ask most often about installation, credits, Detail Ops, and output handling.
What is KuunAI
Explains which problem KuunAI solves, which bridge is available today, and the core gains it creates for users.
The KuunAI approach
KuunAI is a platform approach designed to work around the needs of different software environments and to build a bridge between the current production space and an AI-powered visualization workflow.
In many teams, model production, visualization prep, and presentation output still move forward as disconnected stages. The model is prepared in one tool, decisions are made on another screen, and producing high-quality renders demands extra expertise, extra software, and extra time. That fragmented structure slows the process down and increases the number of repeated attempts.
KuunAI is designed to reduce that separation by living inside the software environment the user already knows. Without leaving the current workspace, the user can move the scene into the render flow, give direction from the same panel, and review the result inside that same loop.
The goal is not only to produce impressive images. The bigger goal is to speed up decisions, make visualization more accessible, and reduce technical barriers so production teams can reach stronger presentation output in less time.

This is an illustrative visual for the main KuunAI panel.
Platform overview
The only active and production-ready bridge today is the SketchUp integration.
In the current release, KuunAI supports a direct render workflow from a SketchUp scene. Inside the panel, the user sets Studio options, adds focused notes for selected areas with Detail Ops when needed, and starts the render from the same interface.
When the render completes, the result lands in Archive. The user can open the latest frame, inspect previous variations, and save the chosen visual. This makes the handoff between modeling and presentation production much more continuous.
Other platform integrations remain part of the product roadmap. New bridges, support scope, and release details will be announced soon.
Available today
The SketchUp bridge already provides scene-connected rendering from the panel, targeted detail guidance, and Archive-based review of results.
Upcoming platforms
Support for additional platforms is planned. Technical scope and release details will be shared soon.

This video block opens directly inside the documentation. It can later be replaced with updated walkthrough videos.
YouTubeCore capabilities
KuunAI is built to make rendering not only faster, but also easier to access and easier to control.
- Users who are not visualization specialists can still produce high-quality renders through a panel that is quick to learn.
- Scene preparation, retry cycles, and render loops can shrink from hours, and in some cases days, down to minutes, and in fast iterations even seconds.
- Installation follows the familiar SketchUp extension pattern and finishes quickly through the RBZ package.
- The Studio tab gathers decisions such as style, resolution, light, sky, season, and environmental character into one central layer.
- Detail Ops makes it possible to focus only on critical materials or model groups instead of redefining the entire scene.
- Archive makes it easier to reopen recent frames, compare versions, and save the most suitable output to local storage.
SketchUp
SketchUp is currently the only live workflow. This section combines plugin installation with the detailed KuunAI usage guide.
1. Download
The KuunAI SketchUp plugin is distributed as an `.rbz` package. The package is prepared for direct installation through SketchUp Extension Manager.
The download link in this document and the download link on the SketchUp product page point to the same source. If the file URL changes, both places should be updated together.
After the download finishes, keeping the RBZ package in an easy-to-reach folder will make installation faster.

Illustrative video slot. It plays inside the document and can later be replaced with newer walkthroughs.
YouTubeThe download link is shared across surfaces. To keep the experience consistent, the SketchUp page and this document should always point to the same file URL.
2. Install through Extension Manager
- 1
In SketchUp, open `Window > Extension Manager`.
- 2
Click `Install Extension` and choose the RBZ file you downloaded.
- 3
Approve SketchUp's security and installation prompt.
- 4
Restart SketchUp if the application asks for it after installation.

You can later replace this area with an Extension Manager screenshot or a step-by-step installation visual.
3. Open the panel and sign in
After installation, open the KuunAI panel and sign in with your user account.
Once sign-in succeeds, the available credit balance appears in the top area and the Studio, Detail Ops, and Archive tabs become active.
From this point on, you can move into the render flow directly from the panel without exporting or preparing intermediate files.
Detailed KuunAI Usage
Because SketchUp is currently the only live KuunAI workflow, this section covers only the in-SketchUp usage steps.
The flow below brings session setup, Studio settings, Detail Ops, and Archive-based render review into a single guide.
When Blender, Maya, and the other coming-soon applications go live, each will have its own installation and usage documentation under its own section.
1. Sign in and prepare your session
The first step is to sign in on the panel with your user account. Once the session opens, account details and the available credit balance are loaded so the system can confirm that you are ready to render.
An active session unlocks the full flow: defining global settings in Studio, adding targeted instructions with Detail Ops, and reviewing completed frames inside Archive.
2. Configure Studio settings
Studio is the main decision layer for a render request. The choices made here affect not only visual style, but also the scene narrative, quality level, and credit usage.
Choosing Studio settings deliberately before rendering leads to more consistent output and makes retry cycles easier to manage. For teams producing multiple variations from the same scene, this area has a direct impact on process quality.
Project Name / Camera
Project Name and Camera help identify the render request, preserve the intended viewing angle, distinguish variations inside Archive, and generate clearer file names when results are saved.
No saved camera yet. Add the current SketchUp angle or render once and it will be saved as "sketchup-scene".
Render Style
Photorealistic delivers balanced and realistic architectural output. Cinematic creates a stronger atmospheric feel and more contrast. Maket Style translates the scene into a physical model language. Pro Maket adds a premium showroom-style presentation.
Output Size
1K uses 25 credits, 1.5K uses 50 credits, 2K uses 75 credits, and 4K uses 100 credits. Lower resolutions are better for fast iteration, while higher resolutions suit stronger final presentations.
Light Position
Switch between Day and Night modes, then use the light dial to choose an hour-like position. Day runs from 06:00 to 18:00, and Night runs from 19:00 to 05:00.
Sky and Season
Sky includes Clear, Soft Clouds, Dramatic, Overcast, Golden Hour, and Storm Light. Season lets you choose Spring, Summer, Autumn, or Winter to define the seasonal tone.
Environment Mood
Rural, Desert, Mountainous, Coast, Tropical, and Meadow influence the environmental character. This setting plays an important role in the scene's background language and sense of place.
3. Use Detail Ops
Detail Ops is built to guide critical areas in a more controlled and professional way instead of sending one broad instruction to the entire scene.
This section becomes especially valuable when you need finer direction over material quality, surface feel, joinery character, roof language, landscape edges, or specific model groups. The user can describe only the important regions instead of redefining the whole scene.
The panel offers two focus types: `Texture` and `Model Group`. Texture focus is used for directions close to a material or surface. Model Group focus targets a more structural area by selecting a group or component inside SketchUp.
Texture focus
Best for subtle adjustments such as material warmth, matte versus gloss, surface texture, weathering, or cladding character.
Model Group focus
Best when you need a more structural intervention on elements such as the main mass, roof group, window frames, landscape boundary, or component-based areas.
Picked list
Keeps selected items in a dedicated list so the user can track which targets already have notes without losing context inside the panel.
Saved descriptions
Each selected item can hold its own instruction. Those instructions are sent together with the render request to improve control over the final output.
- 1
Choose the focus type: `Texture` or `Model Group`.
- 2
Activate the picker icon and click the target area inside the SketchUp viewport.
- 3
Confirm that the selected item appears in the Picked list on the left and becomes visible in the counter.
- 4
Write a clear instruction in the description field on the right that applies only to the selected item.
- 5
Save the description with the arrow icon. Repeat the same process for additional items when needed in the same render request.
- 6
Use `Clear List` whenever you want to reset all selections.

An illustrative visual block reserved for the picker, Picked list, and description area.
From the user's perspective, Detail Ops is a controlled intervention layer built to improve only the necessary regions instead of disrupting the whole scene.
4. Create a render and review it
The final stage starts with `Create Render` and continues with a structured review of the output inside Archive.
When `Create Render` is triggered, the current SketchUp viewport is captured and the render preparation flow begins. The panel automatically switches to Archive so the user stays in the same workspace while waiting for the result.
Once processing is complete, the latest frame opens in the large preview area. If needed, the user can return to recent variations from `Recent Frames` and select a different output again.
If the result is satisfactory, `Save Image` stores the visual on the local disk. This flow keeps retries and variation comparisons much more organized.
Status tracking
The panel manages capture, queueing, and processing internally. The user stays in the same flow until the result arrives.
Archive experience
The `Recent Frames` area makes it easy to reopen recent results and compare closely related versions.
Saving
`Save Image` becomes active once the output is visible and supports a clearer exported file name based on the project name.

An illustrative space reserved for the result preview, recent history, and save flow.

Embedded video area for showing the render-and-review flow directly inside the page.
YouTubePlan details and payments
Collects the main commercial information users need about subscriptions, extra credits, and the payment flow.
1. Plan details
The KuunAI usage model is built around monthly credits. Your plan determines the amount of credits assigned each month as well as certain operational advantages.
In the current structure, Basic includes 1200 credits per month. Pro includes 2400 credits per month. Pro+ also comes with 2400 credits, plus priority queueing, faster turnaround targets, discounted extra credits, and credit rollover benefits.
Basic
Includes 1200 credits per month. It is the entry plan for regular use with the standard queue, standard speed, and core support level.
Pro
Includes 2400 credits per month. It suits users with higher production volume and supports the purchase of extra credits.
Pro+
Uses a premium tier structure billed annually with the equivalent monthly allowance. It combines 2400 credits with priority queueing, faster processing targets, discounted extra credits, and credit rollover.
2. Extra credits
In addition to the monthly plan allocation, eligible plans can purchase one-time extra credit packs. This is especially useful during intensive delivery weeks or when more iterations are needed than expected.
Current top-up packs are offered in 1000, 2000, and 4000 credit options. In the current pricing setup, Pro and Pro+ users have separate pricing levels.
1000-credit pack
Listed at 30 USD for Pro users and 25 USD for Pro+ users.
2000-credit pack
Listed at 50 USD for Pro users and 40 USD for Pro+ users.
4000-credit pack
Listed at 80 USD for Pro users and 68 USD for Pro+ users.
Extra credit purchases are tied to the user account. Because of that, your session should be active before you move into the purchase flow.
3. Payment flow
Activating a subscription and purchasing extra credits both run through a secure web checkout flow that routes the user to the appropriate payment page.
If the user is not signed in, the system first redirects to account creation or sign-in. After authentication, the payment page opens for the selected plan or top-up.
When payment finishes, the user returns to the profile area and the successful transaction updates the plan or credit balance at the account level. Subscription and extra-credit flows are managed inside the same product ecosystem.

You can later replace this area with a pricing view, checkout flow, or a dedicated plan-card visual.
Frequently asked questions
Official answers to the questions KuunAI users ask most often about installation, credits, Detail Ops, and output handling.
What is Detail Ops for?
Detail Ops is not designed to replace the main scene settings. It is designed to guide critical regions in a more controlled way. It becomes the right tool when you want to improve the surface character of a specific material, the expression of a joinery group, or the perception of a particular model part.
A single broad instruction can easily create an effect that spreads too widely across the scene. Detail Ops helps you reach cleaner and more predictable results by letting you attach custom notes to specific targets.
Because multiple targets can be selected in the same render request, the user can send different notes to different areas in one pass. That creates a clear advantage during quality-focused iteration cycles.
How should I choose resolution and credit usage?
For fast tests and decision rounds, 1K or 1.5K should be preferred. For final presentations that require more detail, 2K or 4K is the better fit.
The current credit table is 25 credits for 1K, 50 credits for 1.5K, 75 credits for 2K, and 100 credits for 4K. Separating iteration needs from final-output needs leads to more efficient usage.
Why is Project Name / Camera important?
Project Name and Camera make archive organization much easier, especially for users who create many variations from the same scene.
Together, they make it easier to return to the intended angle, produce clearer file names during save, and keep later output management more organized.
How do I save the final render output?
Once the render is complete, the related frame becomes visible inside Archive. At that point, you can save the visual to your local disk with the `Save Image` button.
If you want to save another recent variation, first reopen that frame from `Recent Frames`, then follow the same save flow.
What should I check first if I have a sign-in issue?
First, verify your account credentials and active connection. Most basic issues are solved in those two areas.
If you forgot your password, the `Forgot Password` link sends you to the web-based reset page. If the issue continues beyond the password itself, verify that the plugin is connected to the right environment and that the session can reach the required backend services.