Applying a Vaporwave visual direction

You are applying Vaporwave to an independent electronic record-label and release archive. Make the archive legible first, then let recovered digital material give it its nostalgic, faintly ironic atmosphere.

What “Vaporwave” means here

Vaporwave is a memory world assembled from discarded consumer-digital material: washed magenta and cyan, obsolete interface chrome, classical forms, checkerboard space, and visible image degradation. It looks backward at the future imagined by late-20th-century consumer culture. It is pale and still, not a dark neon-futurist dashboard.

Recommendations

• Give the fictional label a clear masthead, release index, artist and format metadata, and a short archive note.
• Use a centered axis and calm, symmetrical composition before introducing the retro layer.
• Combine a pale magenta/cyan atmosphere with one restrained obsolete-window convention, a small glitch vocabulary, and original geometric or marble-like forms.
• Keep release names, formats, dates, and explanatory copy clean; distortion belongs to display type and atmosphere only.
• Treat every release, artist, play count, and price as synthetic specimen furniture. Do not imply a real catalogue or audience.
• If Japanese or another non-Latin script is unnecessary, omit it. Never use characters as visual texture.

Avoid

• Dark, kinetic neon cyberpunk or Retrowave shorthand.
• A nostalgia collage with no archive hierarchy.
• Real album covers, recognizable logos, anime frames, statues, or label claims without a verified reuse basis.
• Autoplay audio, fake listener counts, or a transactional flow as the visual subject.
• Glitch effects on body copy, metadata, labels, or controls.

A working order

1. Name the archive job: identify the label and browse a small release index.
2. Establish the centered masthead, release metadata, and reading order.
3. Choose a washed magenta/cyan ground with dark ink that remains readable.
4. Add one obsolete GUI frame as a container for the release field.
5. Draw original classical/geometric media and one visible degradation artifact.
6. Apply channel separation only to display type or non-essential ornament.
7. Keep archive taxonomy and format labels plain and stable.
8. Reflow the release index as a centered stack at narrow widths.
9. Remove any effect that competes with the archive or carries meaning by distortion.

How to check your own work

Confirm that the release index still reads when the glitch layer is removed. Fold the specimen on its vertical axis and check the main composition. Check that the ground is washed rather than vivid, that one artifact remains visible at each breakpoint, and that all archive copy meets 4.5:1 contrast. Verify that any borrowed image or script has documented evidence; otherwise use original synthetic geometry.

Vaporwave — Specification

Definition

Vaporwave is a web-interface style assembled from discarded consumer-digital material: washed magenta and cyan, obsolete interface chrome, classical forms, and visible image artifacts. In this specimen it becomes a synthetic electronic release archive whose calm, centered structure makes the memory layer useful rather than noisy.

Core principles

• Archive before atmosphere. Label identity, release names, formats, and dates remain easy to scan.
• Secondhand material. The surface feels recovered from an obsolete consumer-digital world.
• Degradation is visible but bounded. Copying, compression, or display failure belongs to display treatment and media fields.
• Stillness is structural. The archive is centered and symmetrical like a paused screensaver.
• Washed rather than vivid. Pastel color recalls memory without becoming neon futurism.
• Synthetic and honest. Fictional releases and original geometry never pose as a real catalogue, artwork, or audience.

Visual characteristics

• Pale magenta and cyan atmospheric planes with dark readable ink.
• A quoted obsolete window frame or title bar around the release field.
• Original marble-like geometry, checkerboard perspective, and small chromatic artifacts.
• Clean artist, format, date, and archive-note text.
• Symmetry about a vertical axis and a quiet, centered release index.

Rules

1. Archive hierarchy. The release job comes before the aesthetic layer. Acceptance criterion: A viewer can identify the label, release names, artists, formats, and dates with the artifact layer disabled.
2. Washed palette. Color recalls pastel consumer media rather than neon futurism. Acceptance criterion: The dominant magenta and cyan surfaces use 20–60% saturation and maintain at least 4.5:1 contrast for archive text.
3. Visible degradation. Recovered material shows a controlled failure. Acceptance criterion: At least one non-essential display or media element visibly uses scanlines, channel offset, banding, or compression blocks at every breakpoint.
4. Obsolete interface quote. The archive has a recognizable period container. Acceptance criterion: A release or media field includes a title bar, bevel, scrollbar, or window-frame convention, drawn as original CSS geometry.
5. Classical reference without borrowed rights. The memory world may suggest statuary without importing an unverified asset. Acceptance criterion: The specimen uses original geometric marble-like forms only, or records a verified source and reuse basis in its research dossier; no copied image ships here.
6. Vertical stillness. The primary archive composition holds its axis. Acceptance criterion: The masthead, release field, and release index remain centered on one vertical axis at desktop and narrow container widths.
7. Distortion stays off information. Artifacts never carry the taxonomy. Acceptance criterion: Artist, format, date, archive note, and labels have no channel offset or glitch treatment and remain readable without color-only meaning.

Avoid

• Dark, kinetic cyberpunk or generic Retrowave neon.
• Nostalgia without release hierarchy, or fake plays, listeners, sales, and availability.
• Copied album art, logos, anime frames, or statues without verified reuse evidence.
• Non-Latin characters used as texture rather than meaningful text.
• Glitch effects on archive copy, metadata, labels, or controls.

Acceptance criteria

• The synthetic release archive remains scannable without artifacts.
• Dominant surfaces are washed magenta/cyan with readable archive text.
• One degradation artifact remains visible at each breakpoint.
• An original obsolete GUI convention frames the release field.
• Classical memory is represented by original geometry or documented licensed media.
• The main composition stays centered and symmetrical.
• Archive labels remain unglitched and do not rely on color alone.

Blocking failures

• A glitch effect obscures a release name, format, date, or archive note.
• A copied or unverified image, logo, or non-Latin text is presented as decorative material.
• The retro layer replaces the archive hierarchy or introduces fake audience, commerce, or availability claims.

Responsive adaptation guidance

• Preserve the vertical axis as the release field and index stack; do not collapse into an arbitrary left-aligned dashboard.
• Simplify the obsolete frame and checkerboard geometry rather than shrinking them until their conventions disappear.
• Keep at least one visible artifact and the full plain-text release metadata at every container width.
• Use @container queries scoped to .specimen--site; the archive remains illustrative and has no real transactional controls.