A2UI Express Converter

Convert A2UI Express to A2UI v1.0 JSON and back, compare token savings, and validate against the Basic Catalog.

Private by design

All conversion and validation runs in your browser, on your own device. Nothing is uploaded to any server. Cubbbix never sees your input.

Express characters

0

Express tokens (est.)

0

JSON characters

0

JSON tokens (est.)

0

Token reduction

-

Token counts are estimates only (characters divided by 4), not exact counts from any model tokenizer. Reduction compares Express tokens against JSON tokens.

Basic Catalog signatures

Positional arguments map to these properties in order. A question mark means the property is optional. Use _ to skip an optional property in the middle.

Frequently Asked Questions

A2UI Express is a compact syntax Google introduced on October 27, 2026 for describing user interfaces. Instead of writing verbose A2UI JSON directly, a model writes short one-line statements, and a compiler turns them into standard A2UI v1.0 JSON. Google reports it needs up to 3x fewer tokens than direct JSON.
It converts A2UI Express to A2UI v1.0 JSON and back, using the official A2UI Basic Catalog. It also shows character counts, estimated token counts and the reduction between the two forms, and it validates your input and lists every problem with a line number.
Token counts here are estimates only. The page divides the character count by 4, a rough rule of thumb for English text. Real token counts vary by model and by content, so treat the number as a guide for comparing the two formats, not an exact bill.
All 18 components of the A2UI Basic Catalog: Text, Image, Icon, Video, AudioPlayer, Row, Column, List, Card, Tabs, Modal, Divider, Button, TextField, CheckBox, ChoicePicker, Slider and DateTimeInput. Positional arguments map to catalog properties in schema definition order, exactly as the specification requires.
Unknown components, wrong argument counts against the catalog, undefined variable references, duplicate variable ids, invalid identifiers, a missing surface() call or root component, and malformed Event() calls. Problems are listed with line numbers so you can fix them one by one.
No. All conversion and validation runs in your browser on your own device. Nothing is uploaded to any server, and Cubbbix never sees your input.
Custom catalogs are not supported yet: this page uses the official Basic Catalog only. List _template() helpers are passed through as function calls rather than compiled exactly, and function arguments for less common catalog functions should be given as keyword arguments so they map correctly.

Related Tools

Was this tool helpful?

Comments

Loading comments...

Check Out Other Popular Tools