Wide Text Generator

Create full-width vaporwave aesthetic spaced-out text.

Style

Input

Wide Output

Characters: 0

The vaporwave wide-text aesthetic

“Full width” text comes from East Asian typography, where Latin letters are given the same square width as CJK characters. Those full-width forms live at their own Unicode code points (U+FF01 onward), so the airy, stretched look is preserved anywhere the text is pasted — the hallmark of the vaporwave aesthetic. The spaced-out mode simply inserts a space between characters. Both run fully client-side.

Built and maintained by Meet Shah · Last updated 5 August 2026

What this tool is used for

Producing full-width spaced text for a retro or vaporwave aesthetic.
Styling a short heading in a plain-text field.
Making a phrase visually distinct in a social post.
Producing a decorative label for an image caption.
Testing how a field handles full-width characters.

Frequently Asked Questions

What are fullwidth characters?: The Halfwidth and Fullwidth Forms block (U+FF00-FFEF), created so Latin letters could occupy one full cell in East Asian fixed-width layouts alongside CJK characters — where each character is naturally square.
Why is the spaced-out look associated with vaporwave?: Because the aesthetic borrowed the visual language of 1990s Japanese computing, where fullwidth Latin was routine. The wide spacing is not a stylistic invention — it is a side effect of a genuine typesetting requirement.
Do fullwidth characters compare equal to normal ones?: Not by default, which causes real bugs. Ａ (U+FF21) and A (U+0041) are different code points, so naive comparison fails. Unicode NFKC normalisation folds them together, which is exactly why login forms should normalise input.
Can they be used to bypass filters?: They historically could, and that is precisely why moderation systems now apply NFKC normalisation before matching. Anything relying on this today is likely to be caught, and username systems commonly reject the block outright.
Is there a fullwidth space?: Yes — U+3000 IDEOGRAPHIC SPACE. It is not matched by many whitespace regexes that only cover ASCII space and tab, so it survives trimming and causes puzzling validation failures.
How is it treated by search and screen readers?: Poorly. Search engines normalise fullwidth to ASCII inconsistently, and screen readers may read each character separately or skip them. Anything meaningful should be normal text with styling applied around it.
Do fullwidth characters count as one character?: One code point each, but two columns wide in a monospace or terminal context — so a fullwidth string fits a character limit while overflowing a fixed-width layout. Both facts are true at once.
How do I convert it back?: Unicode normalisation form NFKC maps fullwidth forms to their ASCII equivalents, which is exactly what a search index does. That is also why the disguise is weaker than it looks.

Common errors and gotchas

Using it for body text, which is very hard to read and worse for screen readers.
Expecting search to find it, since full-width characters are distinct from their ASCII forms.
Assuming the width is a style, when it is a different character with its own metrics.
Overlooking that full-width characters can double a field's byte length.
Using it in a value that another system compares against its ASCII original.