Independent reviews. IonBin has no partnerships with the tools on this page and was not paid for these listings. Our evaluations are our own, based on public documentation and our research. Product names are trademarks of their owners and are used for identification only. How disclosure works.

Components / Animated components

Aceternity UI

Use a deliberate visual effect on a marketing surface.

Documentation reviewed

Source review

What this status means

Understand the resource

What it is.

Aceternity UI publishes React, Tailwind CSS and Motion components, blocks and templates. Its animated heroes and presentation pieces can give a page a specific treatment when the content and interaction remain readable.

When it is useful

You need an expressive product presentation and have room to evaluate its cost.

A proposed application

Put it to work.

This example illustrates a possible use. The proposed workflow and expected result are separate from the bounded checks recorded below.

Try this

Add one animated feature treatment, preserve a static reading order, and compare its mobile and reduced-motion versions.

Result to aim for

A distinctive section with a usable fallback.

Before you start

What you need.

  • React, Tailwind and relevant motion dependencies plus performance and accessibility testing.

The practical boundaries

What to watch for.

  • Animation and visual density can consume performance and attention budgets.
  • Inspect the selected component’s license, dependencies and semantics; no component was installed or benchmarked here.

Review record

What we could establish.

  • Public primary documentation and the bounded account-free checks below were reviewed. The 3D-card detail disclosed a visible code block. This confirmed code access, but did not verify the pointer effect, GPU cost or touch behavior.
Source coverage and runtime coverage are separate

The source-review notes describe documentation and identity. The account-free evaluation below records exactly which public interaction or local fixture was checked, what happened, and what remains untested.

Check current access, terms, licensing and data handling before using a resource with your own material.

Runtime and security evaluation

What the evaluation covers.

Limited evaluationAccount-free ·

The 3D-card detail disclosed a visible code block. This confirmed code access, but did not verify the pointer effect, GPU cost or touch behavior.

Methods: Public HTTP response · Public browser sample. A completed check covers the stated sample; it is not a safety certification.

Target
https://ui.aceternity.com/components/3d-card-effect
Version or capture
Unversioned public page checked 2026-10-19
Integrity scope
sha256:75a8a353af2753c8392ec794627a5d9c9964a11fdb417267d033c467991a49d9

Test conditions

  • Chromium 155.0.8059.82 on Windows; fresh temporary profile and fresh account-free contexts.
  • Public HTTPS GET/HEAD requests only; telemetry/auth routes and WebSockets blocked. No account storage or credential environment variables.

Individual checks and observations

  1. Public document and DOM

    pass

    Public browser sample: Fresh Chromium GET, then inspect rendered controls after hydration delay

    Observed: HTTP 200; 6 captured button labels; 0 inputs; 0 canvases.

  2. 3D-card sample disclosure

    pass

    Public browser sample: Inspect public 3D-card preview and open code tab when exposed

    Observed: 0 preview frames; 1 visible code blocks after disclosure. Pointer effect not assumed from code visibility.

Security findings and boundaries

Passive inspection of the public response headers, requested hosts and the named browser sample. No active exploitation, authenticated permissions test or complete security audit.

Observed · caution

Code disclosure is not an interaction test

The bounded sample confirmed that the code could be read. It did not establish that the 3D treatment works with keyboard input, touch or reduced motion.

Practical caveats

  • Keep the card content and primary action usable without the perspective effect.
  • Pin and recheck the selected version or sample before adoption; the observations apply only to the scope and date shown.

What remains untested

  • No local copy, pointer-effect assertion, device frame-rate measurement or full motion-accessibility test.
  • Fresh-browser restrictions can affect external assets and hydration. Initial failed selectors and limited probes remain in the evidence; they are not blanket product failures.

Security limits

  • No authenticated workspace, private content, production backend permissions or data-retention verification.
  • No local copy, pointer-effect assertion, device frame-rate measurement or full motion-accessibility test.

Evaluation sources

  1. Primary public resource
  2. Evaluated public sample

Download this evaluation record (JSON)

Follow the evidence

Sources and further reading.

  1. Primary product documentation

Keep exploring

More in components.

View category

Documentation reviewed

shadcn/ui

Build an owned component layer with documented starting patterns.

Documentation reviewed

coss ui

Start from Base UI-backed product components.

Documentation reviewed

ReUI

Use documented patterns for dense product interfaces.