# Styles The Styles page is your library of brand styles — reference-image style packs that Glossi's AI uses to transform finished renders. A style captures a *look* (color palette, mood, lighting, background treatment) and applies it to any render with one click. Reach it at **Asset Library → Styles**, or directly at [`/library/styles`](https://www.app.glossi.io/library/styles). For the deeper concept and best practices, see Brand Styles. This page focuses on the library-page experience. ### What's on the page * **Toolbar** — Count of styles, search, sort, and a **Create Style** button on the right. * **Style grid** — Each card shows the style's preview image (auto-generated from the reference set) and the style's name. * **Card hover actions** — Favorite, more menu (rename, delete), and a click-through to edit the reference set. A style's preview image is generated automatically once the reference images have been processed. This may take a moment after creation — you'll see a processing indicator on the card until it's ready. ### Creating a style Click **Create Style** to open the create-style flow. There are two ways to build a style: * **Upload reference images** — Provide up to 12 photos or visuals that capture the look you want (color palette, mood, lighting, backgrounds). Glossi processes them and produces a style preview. * **Scrape from a website** — Enter a URL and Glossi extracts product images from the page automatically. You can review the detected images, group similar ones, and turn each group into its own style. Styles are workspace-scoped — every member can use them. ### Filtering and finding * **Search** — Filter styles by name. * **Sort** — Order by recency, name, or other style fields. * **Favorite** — Star styles to keep them surfaced in the Favorites filter and the AI edit panel's top suggestions. ### Editing a style Click any style card to open the edit modal. From there you can: * **Rename** the style * **Add or remove reference images** — The style's preview regenerates after the references change. * **Delete** the style If a style is attached to a pipeline, deleting it doesn't affect existing renders or styled variants — future pipeline jobs will simply skip the deleted style. ### Applying a style Styles are applied to **renders**, not directly from this library page: * **From a render's detail page** — Open a render, pick a style from the **AI Edit** panel, and click Send. Glossi generates a styled variant alongside the original. * **From a pipeline** — Attach one or more styles to a pipeline; every image render will produce additional styled variants — one per attached style. You can apply multiple styles to the same render to compare looks, and you can continue editing styled variants with additional AI prompts. ### Tips * **Use at least 10 reference images per style** — Enough to establish a clear visual direction without introducing conflicting aesthetics. * **Keep references consistent** — All images in a style should share the same mood, lighting, and palette. Mixing very different looks produces inconsistent results. * **Name styles descriptively** — "Warm Studio" or "Clean White" reads better in the AI edit dropdown than "Style 3". * **Test on a single render first** — Apply a new style to one render to verify the result before attaching it to a pipeline that batches dozens of jobs. ### Related * Asset Library Overview * Brand Styles — Concept guide and best practices. * Pipelines — How to attach styles to an automated workflow. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.glossi.io/asset-library/styles.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.