Documentation

Novus Examples is a library of real, downloadable example and test files. Every file is generated by a deterministic script, not collected from the web. That single design choice is what makes the library useful: because a script produced each file, every file ships with an exact specification, a fixed random seed where randomness is involved, and — where it matters — a paired counterpart for before/after testing. Nothing here is copyrighted stock content, so everything is free to use.

Each file has its own page with four things:

• A preview — an inline image, an audio player, or the first lines of a text file.
• A spec table — the file's exact properties: dimensions, colour space, noise sigma and seed, silence timestamps, form field names, encoding, formulas, and so on.
• Purpose tags — what the file is good for testing, each linking to a purpose page.
• One download button — a direct link to the static file. There is exactly one per page.

The spec table is the point. You are testing against a documented input, not a mystery file.

New P6 fixtures add a visible testing contract to the ordinary preview and spec sheet. It names the scenario, the exact result a test should assert, and the artifact's role: valid, recoverable, intentionally invalid, or a reference control. The contract is structured catalog data, so the same expectation appears consistently on file, form, and document-template pages.

Use the contract as the acceptance criterion in a parser, converter, importer, or model-runtime test. The grouped calendar, vCard, metadata, schema, ONNX, and graph suites publish cross-file relationships and expected outcomes instead of asking you to infer behavior from a filename.

A pair is a 1:1 relationship between two files that belong together: a clean image and its noisy version, a colour image and its greyscale conversion, a text document and its image-only scanned twin. Pairs are what serious testing needs — one file is the input, the other is the expected result or the ground truth you score against. When a file has a pair, its page links straight to it.

A group ties together a family of files that share the same content: one test card exported across PNG, WebP, AVIF, and more, or a resolution ladder from 16px to 4K, or a template offered as both DOCX and PDF. Groups are how you test converters — convert one member and diff against the expected twin.

Every file is tagged with what it helps you test. Browse them under Browse by purpose: denoise testing, CSV parsing, OCR, auto-trim, form parsing, encoding detection, and more. Purpose pages are the fastest way to find the exact fixtures for a task.

Every file in the library is free for any use, with no attribution required — including commercial use. See the license for the plain-language terms. The intentionally corrupt files are provided as-is for error-handling tests; they are not valid files by design and are clearly labelled as such.

File URLs, ids, and download paths are permanent. Once a file ships, its address never changes. That means you can link to a fixture from a README, embed its download URL in a CI pipeline, or bookmark it, and it will keep working.

Because every download is a static URL, you can fetch fixtures directly in a test pipeline:

curl -O https://examples.novusstreamsolutions.com/files/data/csv/messy-csv-quoted-commas-newlines.csv

Point your parser, converter, or filter at the downloaded file and assert against the documented spec. For paired fixtures, download both the input and its reference and score one against the other. Nothing requires an account or an API key.

Create is the shared starting point for the site's six local-first creation models:

• Text and data — start with the blank buffer or a format starter in the editor, then preview, convert, and download.
• Forms — open any of the 243 catalog fixtures in Form Studio. HTML and PDF use layout editors; JSON, CSV, TXT, FDF, and XFDF use honest field-value editors with original-format export and re-import.
• Documents — start with a blank block shell or one of 36 editable curated families in Document Studio, then export HTML, Markdown, DOCX, XLSX, or print to PDF. A definition with exactly one table can also export CSV without inventing a multi-table flattening rule.
• Visuals — start from the blank canvas or choose a validated scene in Visual Template Studio, edit its text, tables, shapes, colours, logos, and images, then export locally.
• Audio — synthesize a tone, sweep, seeded noise signal, or silence in the audio workspace, then export a PCM or encoded test fixture with recipe, source, and output SHA-256 evidence.
• Video — synthesize colour bars, a countdown, or a motion grid in the video workspace, using only codecs reported by this browser session.

The workspaces share an entry point and local-first privacy model, but keep separate editors because their contracts differ. A CSV cell, an AcroForm widget, a document block, and a positioned canvas node should not silently coerce into one another.

The audio and video creation workspaces generate synthetic fixtures only. They never request a camera or microphone, accept an upload, create an account, or send source media to a server. Each job runs in a dedicated module worker that is created only after Generate is pressed and is terminated on completion or cancellation. Recipe limits cap memory and output size.

The workspaces pin Mediabunny and its official MP3, AAC, FLAC, and AC-3 extensions at version 1.51.0. Mediabunny and its extensions use the Mozilla Public License 2.0. The MP3 extension embeds LAME 3.100 under the LGPL; the AAC and AC-3 extensions use size-limited FFmpeg encoder builds; the FLAC extension uses libFLAC. The site does not bundle stock ffmpeg.wasm. Full notices are recorded in docs/MEDIA_ENCODER_NOTICES.md in the source repository.

PCM and pinned encoder-extension paths use the byte reproducibility tier for a fixed recipe and package version. WebCodecs video and browser-provided Ogg encoders use the content tier: recipe, source fingerprint, duration, dimensions, and codec intent are stable, while encoder bytes can vary by browser, operating system, and hardware. The output SHA-256 records the exact artifact produced by the current session; it is not a claim that every conforming browser emits identical bytes.

The faceted browser can collect up to 100 files and 200 MiB on the current device. Export produces a deterministic ZIP with a sorted manifest and SHA-256 values. The selection is stored only in browser storage; files are fetched from their existing static download URLs when you export the bundle. No collection, manifest, or fixture is uploaded to a Novus server.

Form and Document Studio can retain a local draft. Visual Studio can retain user-selected image assets in the browser's IndexedDB. These are convenience copies on the current device, not accounts or cloud saves. Clear the draft in its workspace or clear this site's browser data to remove them. Generated media remains in memory only long enough to preview or download it, and object URLs and worker resources are released on completion, cancellation, retry, or page close.

Templates covers two product surfaces:

• Document templates — invoices, CVs, spreadsheets, decks, and HTML email starting points (same permanent /templates/... download URLs as before).
• Visual templates — product studio, lifestyle, marketplace, social, and marketing scenes under /visual-templates. Published families only appear after real previews, size exports, variants, and an editor scene pass validation.

Visual Template Studio opens either a published scene or an empty canvas so you can add or replace images and backgrounds, edit text, tables, shapes, and palette colours, and export PNG/JPEG/WebP/SVG locally. Uploads stay in the browser. Start blank when you want to build every layer yourself, or use a validated template when its tested layout is the better starting point.

The catalog includes 840 scene-backed families, including dedicated Software/SaaS Product Marketing and Travel, Tourism & Hospitality collections. Each detail page explains what the scene is best for, which fields are editable, how to customize it, available exports, and related templates; every visible preview element must have a corresponding editable scene node.

The model inference testing suite groups each validated ONNX model with JSON input and expected-output artifacts. The page contract records tensor shapes, dtypes, opset, numeric tolerance, and the expected operation, while the model page exposes a graph preview. That makes each trio usable as a small runtime compatibility test rather than a generic binary download.

Beyond denoise and format ladders, the Images library includes paired suites for photo restoration, inpainting, deblur, super-resolution, and background removal (including hard-edge cases). Use them as inputs and ground truth when measuring filters and models.

Browse the Images, Audio, Documents, Data, and Templates libraries, explore visual templates, search from any page, or open a text file directly in the in-browser editor.