WYSIWYG — What You See Is What You Get: definition, history, and uses

Core characteristics

Typical WYSIWYG editors combine an interactive canvas with tool palettes, style controls, and immediate rendering. Users arrange text, images, and other elements directly, and the editor translates those actions into a formatted result. For print-oriented tools the goal is matching paper output; for web tools the goal is reproducing browser rendering. For print examples see a printed document preview via print preview. For web output the editor attempts to mirror a web page display.

Brief history and development

The idea of editing in a visual, document-like mode emerged with graphical user interfaces and research systems at early labs and in the first consumer software. Early word processors and desktop-publishing applications popularized the model because they let non‑technical users compose complex layouts. Over time the concept expanded from desktop publishing to web design tools, presentation software, and even multimedia control consoles.

Common uses and examples

• Word processors and desktop-publishing applications for books and brochures.
• Slide and presentation editors such as those that output to a PowerPoint-style format.
• Web-based rich-text and site builders that try to hide underlying HTML/CSS.
• Specialized consoles that let operators design visual effects or lighting cues, where the interface mirrors the live result (lighting consoles).

Limitations and notable distinctions

WYSIWYG simplifies layout but can obscure underlying structure or code. For web content, what appears in the editor may differ across browsers and devices, and responsive behavior is hard to convey. Editors that prioritize visual appearance sometimes produce bloated or non‑semantic code. For these reasons some workflows prefer markup-first approaches such as source editing or the WYSIWYM ("What You See Is What You Mean") philosophy, which separates content structure from final presentation.

Best practices balance visual editing with access to the underlying source, previews for target formats, and attention to accessibility and semantics. Modern systems often offer both a graphical view and a source view so users can combine the immediacy of WYSIWYG with the control of code-based editing.