Seamless Logo Marquee
An infinite horizontal logo scroll with masked edges, a pause-on-hover affordance and a reduced-motion fallback that wraps instead of moving.
One unbordered line of wordmarks beside a claim you can actually be wrong about, sized to sit under a hero without pushing the CTA down or moving while the headline is being read.
components/logo-strip.tsxnpx hoverlab add logo-strip
Or over MCP, from your editor's agent — no account needed.
Free to read, copy and install, for personal and non-commercial projects. Shipping it in client work or a paid product needs Pro ($79 once). The source lands in your repo and stops being ours — no attribution, nothing to upgrade.
Start a page with this section — add more, order them, and leave with the page source.
Trusted by 4,000+ engineering teams
Rendered live in your current theme — this is the same component whose source is below, not a screenshot of it.
/**
* <LogoStrip> — the one line of proof that sits directly under a hero.
*
* The catalog already has two logo sections and neither fits this slot.
* <LogoCloud> moves, and motion immediately below the fold competes with
* the headline it is supposed to support. <LogoGrid> is a bordered block
* with real presence — correct on a customers page, far too heavy as the
* second thing on a landing page, where it pushes the primary CTA down and
* reads as a section rather than as a footnote to the hero.
*
* So this one is deliberately the smallest of the three: one row, no
* border, no card, no motion, tight vertical padding. It is meant to be
* skimmed in half a second and then scrolled past, which is exactly what
* social proof under a hero is for.
*
* The count is the part people leave out. "Trusted by great teams" is
* something any site can say; "Trusted by 4,000+ teams" is a number that can
* be wrong, which is why it is worth reading. `claim` takes the whole
* sentence rather than a number and a template, because the honest phrasing
* differs — some products count teams, some count engineers, some can only
* honestly name six companies and should say six names and no number.
*
* Logos wrap and centre rather than scrolling. A strip that overflows on a
* phone has hidden its last two names from the readers most likely to be on
* one, and there is no arrow to tell them so.
*
* Text wordmarks by default, matching <LogoGrid>: remote SVGs cost a layout
* shift, a set of licences and a request each, and the shape reads the same
* without them. Pass nodes when the real marks matter.
*/
import * as React from 'react'
import { ArrowRight } from 'lucide-react'
export interface LogoStripProps {
/** The whole sentence, not a number and a template. See above. */
claim?: string
/** Wordmarks, or any node — an <img>, an inline <svg>. */
logos?: React.ReactNode[]
/** Optional route to the page that backs the claim up. */
moreHref?: string
moreLabel?: string
/** Hairline above the strip, for separating it from the hero. */
divided?: boolean
className?: string
}
const DEFAULT_LOGOS = ['Northwind', 'Contoso', 'Umbra', 'Lumon', 'Vandelay', 'Aperture']
export function LogoStrip({
claim = 'Trusted by 4,000+ engineering teams',
logos = DEFAULT_LOGOS,
moreHref,
moreLabel = 'Read their stories',
divided = true,
className = '',
}: LogoStripProps) {
return (
<section
aria-label="Customers"
className={`w-full ${divided ? 'border-t border-border/60' : ''} ${className}`}
>
<div className="mx-auto flex w-full max-w-6xl flex-col items-center gap-6 px-4 py-10 sm:px-6 lg:flex-row lg:gap-12 lg:px-8">
<p className="shrink-0 text-center text-sm font-medium text-muted-foreground lg:text-start">
{claim}
</p>
<ul className="flex flex-1 flex-wrap items-center justify-center gap-x-10 gap-y-4 lg:justify-start">
{logos.map((logo, i) => (
<li
key={i}
className="text-lg font-bold tracking-tight text-muted-foreground/85 transition-colors hover:text-muted-foreground"
>
{logo}
</li>
))}
</ul>
{moreHref ? (
<a
href={moreHref}
className="group flex shrink-0 items-center gap-1.5 text-sm font-medium text-primary focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-ring focus-visible:ring-offset-2 focus-visible:ring-offset-background"
>
{moreLabel}
<ArrowRight
aria-hidden
className="h-4 w-4 transition-transform motion-safe:group-hover:translate-x-0.5 rtl:rotate-180 rtl:motion-safe:group-hover:-translate-x-0.5"
/>
</a>
) : null}
</div>
</section>
)
}
bg-card, text-muted-foreground) — it inherits your theme instead of overriding it.Drop it at components/logo-strip.tsx and import it where you need the section:
import { LogoStrip } from '@/components/logo-strip'3 of this block’s props are simple enough to drive from here. Change them and the block below re-renders — it is the same component whose source is above, not a mock of it. Everything else it accepts is in the table underneath.
Read out of the component’s own type and signature, so this cannot drift from the source below. Every prop has a default — the component renders standalone before you pass it anything.
| Prop | Type | Default |
|---|---|---|
claimThe whole sentence, not a number and a template. See above. | string | 'Trusted by 4,000+ engineering teams' |
logosWordmarks, or any node — an <img>, an inline <svg>. | React.ReactNode[] | DEFAULT_LOGOS |
moreHrefOptional route to the page that backs the claim up. | string | — |
moreLabel | string | 'Read their stories' |
dividedHairline above the strip, for separating it from the hero. | boolean | true |
className | string | '' |
The same block rendered once to markup, wrapped as a file your framework compiles. Tailwind classes are framework-agnostic, so the design transfers intact — the behaviour does not.
<!--
Under-Hero Logo Strip — markup from the Hoverlab catalog.
This is the block rendered once to HTML and wrapped as a component
file. It is not a port of the React source: the Tailwind classes carry
the design, which is the part that took the work, and they are the same
in every framework.
This block has no interactive behaviour, so nothing is missing.
-->
<section aria-label="Customers" class="w-full border-t border-border/60 ">
<div class="mx-auto flex w-full max-w-6xl flex-col items-center gap-6 px-4 py-10 sm:px-6 lg:flex-row lg:gap-12 lg:px-8">
<p class="shrink-0 text-center text-sm font-medium text-muted-foreground lg:text-start">Trusted by 4,000+ engineering teams</p>
<ul class="flex flex-1 flex-wrap items-center justify-center gap-x-10 gap-y-4 lg:justify-start">
<li class="text-lg font-bold tracking-tight text-muted-foreground/85 transition-colors hover:text-muted-foreground">Northwind</li>
<li class="text-lg font-bold tracking-tight text-muted-foreground/85 transition-colors hover:text-muted-foreground">Contoso</li>
<li class="text-lg font-bold tracking-tight text-muted-foreground/85 transition-colors hover:text-muted-foreground">Umbra</li>
<li class="text-lg font-bold tracking-tight text-muted-foreground/85 transition-colors hover:text-muted-foreground">Lumon</li>
<li class="text-lg font-bold tracking-tight text-muted-foreground/85 transition-colors hover:text-muted-foreground">Vandelay</li>
<li class="text-lg font-bold tracking-tight text-muted-foreground/85 transition-colors hover:text-muted-foreground">Aperture</li>
</ul>
</div>
</section>
What each framework gets across the whole catalog — effects convert properly; this rung is markup.
The component, its props, the design tokens it expects and the command that installs it — as one prompt. Paste it into Claude, Cursor, v0 or ChatGPT and what they build around it will match the rest of the catalog instead of inventing its own system.
Want the whole screen instead of this one section? Open a page and copy it entire.
All of them free to read, copy and install — no account, no locked tiles, no watermarked preview. The whole catalog is open, and so are the API and the CLI.
Browse Logo CloudsCopying the code is free. Putting it in client work or a paid product is what Pro is for — the licence, not the access.
An infinite horizontal logo scroll with masked edges, a pause-on-hover affordance and a reduced-motion fallback that wraps instead of moving.
Hairline-separated cells that hold still and show the whole set at once — the logo wall for a footer, a customers page, or anywhere the count is the claim.
Customer logos under segment headings as a description list, with an “and 40 more” count for the ones under NDA — answers whether you have done this for someone like the reader, which a flat wall cannot.