v2.4.1 // Updated Q3 1998

Preservation Guidelines

Standards for capturing, validating, and maintaining early web artifacts. These protocols ensure historical accuracy, technical integrity, and long-term accessibility of our digital heritage.

Core Principles

Every artifact in the 1990 Web Archive is evaluated against four foundational pillars. These principles guide our curation, restoration, and public access strategies.

  • Authenticity: We preserve content exactly as it existed in its original runtime environment. No modernization of code, typography, or layout occurs without explicit archival notation.
  • Completeness: Archives must include all linked assets (images, scripts, style sheets, embedded objects) and renderable states. Partial captures are flagged for recovery.
  • Accessibility: While historical fidelity is paramount, we provide alternative metadata, structural outlines, and descriptive transcripts to ensure researchers and assistive technologies can navigate legacy content.
  • Ethical Stewardship: We respect the digital footprint of early web communities. Harmful, non-consensual, or legally restricted material is quarantined or redacted in accordance with preservation ethics and applicable law.

Technical Specifications

Our capture and storage pipeline is calibrated for the technological landscape of 1990–1999. Archives must comply with the following standards.

Markup & Structure

  • HTML Versions: HTML 2.0 (1995), HTML 3.2 (1997), HTML 4.01 Transitional (1999). Framesets, applets, and legacy form elements are fully supported.
  • CSS: CSS Level 1 (1996) and early Level 2 properties. Background images, text colors, and table styling are preserved. CSS2.1+ is normalized but flagged.
  • Encoding: ISO-8859-1, Windows-1252, Shift_JIS, and early UTF-8. BOM and charset declarations are preserved and validated.

Media & Assets

Asset TypeSupported FormatsNotes
ImagesGIF, JPEG, BMP, early PNGAnimated GIFs stored as single multi-frame files. LZW patents noted.
AudioMIDI, WAV, AU, early MP3MIDI SysEx and patch sets archived alongside tracks.
Video/PluginsQuickTime, RealVideo, Shockwave, Flash (v1–v4)Emulated via legacy VM snapshots. Original binary wrappers preserved.
FontsWeb-safe early set (Times, Arial, Courier, Georgia, Verdana)Custom @font-face unsupported in era; fallbacks documented.

Metadata Schema

Each archived node is assigned a Dublin Core-compliant metadata block, extended with era-specific fields:

{
  "dc:title": "Welcome to My Homepage",
  "dc:creator": "unknown_author",
  "dc:date": "1996-08-14",
  "dc:format": "text/html; charset=iso-8859-1",
  "archive:era": "pre-y2k",
  "archive:tech_stack": ["html3.2", "tables", "bg-sound"],
  "archive:host": "geocities.com",
  "archive:capture_method": "wget-mirror-v1.5"
}

Archiving Workflow

Content moves through a strict five-stage pipeline before entering the public index.

  1. Discovery: URLs are sourced from link lists, Wayback snapshots, Usenet postings, and community submissions.
  2. Capture: Deep crawling with depth-limited recursion. Assets are fetched via era-appropriate user agents (Netscape 3.0, IE 4.0, Mosaic).
  3. Validation: Syntax checking, broken link auditing, and asset integrity verification (MD5 checksums). Fails trigger re-crawl or manual recovery.
  4. Storage: Triple-redundant cold storage across geographic nodes. Files are immutable and cryptographically signed.
  5. Verification: Render comparison against reference screenshots. Access endpoints are provisioned with sandboxed legacy interpreters.
Note: Automated pipelines run weekly. Manual review occurs for high-priority cultural artifacts, commercial sites, and educational resources.

Contributor Guidelines

We welcome donations from digital historians, former webmasters, and preservationists. Follow these standards for acceptance:

Submission Format

  • Zip archives containing original HTML files and a mirrored /assets/ directory.
  • Include a README.txt with provenance, approximate date, and any known hosting history.
  • Do not modify original source code. If files are corrupted, provide the corrupted version alongside any reconstructed copies.

Acceptance Criteria

We prioritize content that demonstrates:

  • Historical significance in web design, early commerce, or online community building
  • Technical novelty (early CGI, JavaScript experiments, client-side frameworks)
  • Cultural documentation (fan sites, hobbyist hubs, early educational portals)
Rejected Content: Malware, phishing templates, non-consensual personal data dumps, and active commercial sites still hosting sensitive user information.

How to Submit

Upload packages via our secure portal or send encrypted tarballs to submit@1990webarchive.org. All submissions are reviewed within 14 business days. Contributors retain intellectual property rights; we claim only preservation and research usage rights.

"}