What you can do with Glossi

Glossi connects product preparation, 3D art direction, repeat production, controlled adaptation, and delivery. This page is the map of the shipped product: what each part does, why it matters, and where to learn the workflow.

Prepare a reusable product

A model is more useful when it carries the state needed for the next scene, finish, or configuration.

• Upload common 3D and CAD formats in the browser or through the API. Glossi converts source geometry into a form the live Studio can use. See Supported file types.
• Generate a starting model from product photos when no 3D file exists. Generated geometry still needs review before production. See Model library.
• Track processing and preview state so you know when a product is ready to use.
• Choose converted versions and separate product parts so materials and configurations can address the correct regions.
• Calibrate scale, position, rotation, and component mapping once, then reuse that prepared state in other projects.
• Use modeled options and poses when the source product includes them.
• Map material groups and save material-swap rules so a meaningful region such as an upper, frame, or trim can receive the right finish.
• Export a prepared model when it needs to move into another 3D workflow.

Prepare a 3D model

Direct the product in a live 3D studio

Studio streams a live Unreal Engine session to the browser. It keeps product control close to the final image instead of hiding it behind an offline render cycle.

• Edit product materials by selecting the product region, applying a library material, and tuning supported properties.
• Control transparent and glass materials with dedicated opacity and refraction settings where supported.
• Save a tuned material to the library so the finish can be reused.
• Build and save lighting rigs, use presets, adjust global light behavior, and apply IES profiles for supported physical lights.
• Choose and customize backdrops for clean catalog frames or richer environments.
• Add props and override prop materials without importing the object again for every scene.
• Place cameras and camera targets around meaningful product points.
• Save image angles and return to the same framing later.
• Create video clips and manual motion for cameras, products, and supported lights.
• Undo and redo supported Studio actions while exploring.

Learn the Studio

Preserve approved direction

The scene behind an accepted image can become a reusable production setup instead of a screenshot or a loose brief.

• Save a project as a template with its scene, lighting, camera views, clips, and output intent.
• Create template versions so later changes do not silently alter an existing production run.
• Pin a project to a specific version for reproducible output.
• Lock shared templates when approved direction should be protected.
• Build reusable material and prop libraries from workspace assets or curated catalog entries.
• Keep material versions and return to an earlier approved state.
• Save AI Styles and layout guides so post-production direction does not depend on reconstructing a prompt.

Work with templates and browse the asset library

Produce images and video

Use the same prepared product and approved setup through the production lane that fits the job.

• Render high-resolution stills from selected image angles.
• Render video from saved clips in the same project.
• Choose product options, views, aspect ratios, resolution, and supported transparency settings for the requested output.
• Start multi-view render requests instead of exporting each capture separately.
• Use Quick Render to apply an approved template to one or more prepared models without reopening Studio for every item.
• Group repeated project work with Batch Projects where the workspace plan exposes that flow.
• Inspect progress, retry failed work, and cancel active work from durable render state.
• Preserve completed captures during supported recovery paths when a multi-output render is interrupted.
• Retrieve finished files through time-bound download links and keep them organized in the render library.
• See render and AI usage history where the workspace plan exposes metering.

Export from Studio, use Quick Render, or manage the render library

Review and adapt finished work

A render remains connected to its source and version history after production.

• Create prompt-directed image edits as child versions of the original render.
• Apply a saved style reference to build a related visual family.
• Combine prompts, references, annotations, layout guides, and lighting direction in one edit request.
• Mark the exact region that should change instead of describing its location only in text.
• Generate several candidates and compare product placement in supported image-edit workflows. This reduces drift; it does not guarantee product fidelity.
• Animate a still image or apply supported generative changes to an existing clip.
• Generate reusable material imagery and channels from the material workflow.
• Compare versions, revert to an earlier version, or remove a derivative without losing the original render.
• Attach threaded comments to an exact visual region and version for authenticated collaborators.

Edit a render with AI and review versions and comments

Automate repeated production

Automations apply product-aware steps to new work from a folder, event, or manual run.

• Start manually, from a watched folder, or from supported product and render events.
• Build a directed workflow from supported template, render, style, AI-edit, and export stages.
• Branch work into multiple output paths when one input needs several approved results.
• Connect Google Drive, OneDrive, or Adobe Experience Manager for supported input and output folders.
• Inspect runs, stage state, and failures, then retry or cancel supported work.
• Use the REST API for model intake, project creation, render execution, status, cancellation, and signed retrieval.
• Use idempotency keys on supported API writes so a safe retry does not create a duplicate object.
• Receive signed webhooks for supported model, project, job, render, and pipeline events.

Material-swap and direct-colorway automation paths are still constrained. Validate the exact node sequence before relying on it for unattended production.

Build an automation, connect a source, or start with the API

Deliver and publish

Production is complete when an approved output or configured product reaches the person or system that needs it.

• Download finished images and videos from the render library.
• Export supported automation results to connected Drive, OneDrive, or AEM folders.
• Notify another system through signed webhooks. Webhooks do not currently provide guaranteed or exactly-once delivery, so consumers should verify state and tolerate duplicate events.
• Publish a branded Showroom from approved product projects.
• Expose approved product options and allowed surface materials without exposing every internal Studio control.
• Reuse saved views and 360 playback as customer-facing navigation.
• Persist a selected Showroom configuration in the URL. A dedicated public share workflow is not yet complete.

Configure Showroom or implement webhooks

Work as a team

• Organize work in a workspace with members and role-aware access.
• Issue, expire, revoke, and restrict API keys for service-to-service production.
• Inspect cross-workspace usage where an organization role and plan expose reporting.
• Export account metadata or delete an account through supported lifecycle controls.

Enterprise plan language can include commercial commitments that are not product features. Confirm identity, security, compliance, capacity, and service requirements with the Glossi team before treating them as available technical controls.

The shortest path to value

1. Produce one accepted image from a real product.
2. Save the approved project as a template.
3. Apply that template to a second prepared product with Quick Render.
4. Review the outputs and deliver them to their destination.

The first image proves control. The second useful result proves that the work can compound.

Make your first image