> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/dforms/design/client-logos.md). # Client logos marquee Show a "Trusted by" marquee of client logos on your dForms form cover, on the reveal screen, or on both. Add up to 24 logos with a name and an image URL. Social proof works on forms too. The client logos marquee is a scrolling "Trusted by" strip of logos that you can show on the cover screen, on a reveal screen, or on both. Each logo is just a name and an image URL; no upload needed. *** **Step 1:** Open your form, open the **Design** tab and scroll to the **Client logos** section. Make sure **Show the marquee** is on, then choose where it appears with **Show the marquee on**: **Cover**, **Reveal screen** or **Both**. **Step 2:** Click **Add logo**. A row appears with two fields: **Name** and **Image URL**. Type the client's name and paste a public link to its logo (PNG, SVG or JPG). Repeat for each logo; the trash icon (**Remove logo**) deletes a row.

Three logos added. The live preview on the right already shows the Trusted by strip under the cover text.

> **💡 Tip:** Pick logo files that read well on your form's background. On a dark theme, use white or light versions of the logos; on a light theme, use the dark versions. If an image cannot load, the marquee shows the **Name** instead, so always fill it in. **Step 3:** Click **Publish** and open the public link. The logos scroll continuously under the cover copy, labeled **Trusted by**.

The published cover with the Trusted by marquee of logos scrolling under the headline and above the Start button — The published cover with the **Trusted by** marquee. It loops automatically; respondents do not have to scroll it.

## Settings | Setting | Options | What it does | | ------------------------------ | ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | | **Show the marquee** | On / Off | Master switch. Off hides the strip everywhere without deleting your logos. | | **Show the marquee on** | **Cover** / **Reveal screen** / **Both** | Where the strip appears. **Reveal screen** puts it under the reveal animation while the respondent waits; **Both** shows it in both places. | | **Name** | Free text | The client's name. Used as the image's alt text, and shown as a text chip when no image is set or the image fails to load. | | **Image URL** | `https://…` | A public link to the logo file. | | **Add logo** / **Remove logo** | | Add a row (up to 24 logos) or delete one. | ## Good to know * **The marquee needs a place to show.** With scope **Cover** it only appears when **Show a cover screen** is on (see [Cover screen & banner](/dforms/design/cover-screen-and-banner.md)). With scope **Reveal screen** it appears on your reveal steps (see [Reveal screens](/dforms/logic/reveal-screens.md)). A form with no cover can still scope its logos to the reveal. * **Brand kit logos.** Your workspace [Brand kit](/dforms/design/brand-kit.md) also has a **Client logos** list. New forms start with those logos; a form that has its own list uses its own. * **Empty list.** If the list is empty, the section reads **No client logos yet.** and nothing is rendered, even with the switch on. ## What's next * [Cover screen & banner](/dforms/design/cover-screen-and-banner.md) * [Reveal screens](/dforms/logic/reveal-screens.md) * [Brand kit (workspace-wide)](/dforms/design/brand-kit.md) * [Logos, layout & transitions](/dforms/design/logos-layout-transitions.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.dapta.ai/dforms/design/client-logos.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.