Question 1

What is the difference between a supercar and a hypercar?

Accepted Answer

A supercar is a high-performance exotic vehicle category, often produced in larger numbers and spanning multiple price tiers. A hypercar is typically the next rung up: it’s a halo-level vehicle with extreme performance targets, cutting-edge materials (carbon monocoques, active aerodynamics), and usually limited production. In practice, “hypercar” is also a market label—brands use it to signal their most advanced or most exclusive road cars. For directories and inventory, it helps to tag both the broad segment (supercar/exotic) and the halo segment (hypercar) so users can filter accurately.

Question 2

How do I embed hypercar brand logos from Motomarks in my site or app?

Accepted Answer

Use the Motomarks Image CDN and reference the brand slug in the URL. For compact lists (like this directory), prefer badge logos:

- Badge (recommended for lists): `https://img.motomarks.io/pagani?type=badge`
- Full logo (good for hero areas): `https://img.motomarks.io/pagani`
- Wordmark SVG (crisp on any screen): `https://img.motomarks.io/pagani?type=wordmark&format=svg`

You can also set size (xs–xl) and format (svg/png/webp). For implementation guidance, caching behavior, and parameters, see /docs.

Question 3

Which logo format should I use for performance and clarity—SVG, PNG, or WebP?

Accepted Answer

It depends on where the logo appears:

- **SVG**: Best for wordmarks and vector-friendly marks when you need perfect sharpness at any size (especially on high-DPI screens). SVG is ideal for UI components that scale.
- **WebP**: Great default for most web use because it’s compact and fast, especially for badge icons in directories.
- **PNG**: Useful when you need broad compatibility or specific raster workflows.

A practical approach is: use **WebP badge** for lists and filters, and **SVG wordmark** for headers or brand pages where crisp typography matters. Motomarks lets you choose per use-case via query parameters.

Question 4

How do I handle brand name variations like “Mercedes Benz” vs “Mercedes-Benz” in my database?

Accepted Answer

Treat the display name and the canonical identifier as separate fields. Store a canonical **slug** (e.g., `mercedes-benz`) and map all input variants to that slug during ingestion. Keep a lookup table with aliases and common misspellings, and only use the slug to request images (and, if applicable, API data). This prevents duplicate brands from appearing in filters, improves search quality, and keeps logo retrieval consistent. Motomarks pages like /glossary/brand-slug help define a repeatable convention for your team.

Hypercar Car Brands Directory

How this hypercar directory is organized

Hypercar brands (logos + quick identifiers)

Main hypercar marques and hypercar-producing brands

Categorization tags (suggested)

Logo usage: badge vs wordmark (and why it matters)

Data hygiene tips for hypercar brand catalogs

Frequently Asked Questions