Community program

Introducing UWC+

The exotic formats program. UWC covers the popular 99% — UWC+ is how the remaining 1% gets in: you request a format, we build it. Free, like everything here.

What UWC+ is about

Free forever

No paywall, no premium tier. UWC+ is a process, not a product: requested formats land in the main converter for everyone.

Privacy first

Your example files are used only to build and test the converter. Nothing is stored — same policy as the whole service.

Built by demand

We don't chase formats nobody needs. If you ask, it's real demand — and your issue becomes the spec.

How it works

1
You open a GitHub Issue with the format description and an example file (template below).
2
We check the spec: is it documented, is there a license-compatible parser, or can it be hand-written.
3
The converter gets built — client-side when possible, server-side for heavy formats.
4
The issue closes with a release note. Your format is now in UWC for everyone.

What a good request looks like

Four things turn «add X pls» into a converter. The first one is mandatory — without it the issue is closed.

Format description — required

Link the specification, RFC, docs or describe the structure yourself: delimiters, escaping, types. Without this the request cannot be evaluated.

Example file

A small real-world sample (or synthetic, if the data is sensitive). This becomes the round-trip test.

Conversion direction

X → JSON? JSON → X? Both ways? For which target — CSV, YAML, text?

Use case

One sentence about where this format comes from. Helps prioritize and pick the right tier (browser vs server).

Issues like «add .toon to .json pls» are closed as invalid — without a format description there is nothing to implement. A spec link or your own description is the entry ticket.

Issue examples

Will be accepted

### Format
TOON (Token-Oriented Object Notation)

### Specification / description
A compact text format for LLM prompts: like JSON but ~40% fewer tokens.
Spec: https://github.com/toon-format/spec — objects are `key{a,b}:` blocks,
arrays are comma-separated rows. Human-readable, lossless round-trip to JSON.

### Example file
```toon
users[2]{id,name}:
  1,Alice
  2,Bob
```

### Desired conversion
TOON → JSON and back (two-way). I have ~200 files in this format from our LLM pipeline.

Will be closed

add .toon to .json pls

No spec, no example, no direction. Even knowing what TOON is, we'd have to guess the exact dialect, escaping rules and edge cases — that's how broken converters are born.

Ready to request?

Open a GitHub Issue using the template — copy the good example above and fill in your format. Issues are triaged weekly.

Open an issue

Requires a free GitHub account. Issues are public — check existing ones first to avoid duplicates.