title: Overview category: builds-guides
CKEditor 5 Builds are a set of ready to use rich text editors. Every "build" provides a single type of editor with a set of features and a default configuration. They provide convenient solutions that can be installed with no effort and that satisfy the most common editing use cases.
The following CKEditor 5 Builds are currently available:
Classic editor is what most users traditionally learnt to associate with a rich text editor — a toolbar with an editing area placed in a specific position on the page, usually as a part of a form that you use to submit some content to the server.
During its initialisation the editor hides the used editable element on the page and renders "instead" of it. This is why it is usually used to replace <textarea> elements.
In CKEditor 5 the concept of the "boxed" editor was reinvented:
<iframe> element) — it is now much easier to style it.{@img assets/img/editor-classic.png 772 Screenshot of a classic editor.}
To try it out online, check the {@link examples/builds/classic-editor classic editor example}. Jump to {@link builds/guides/quick-start#Classic-editor quick start} to start using it.
Inline editor comes with a floating toolbar that becomes visible when the editor is focused (e.g. by clicking it). Unlike classic editor, inline editor does not render instead of the given element, it simply makes it editable. As a consequence the styles of the edited content will be exactly the same before and after the editor is created.
A common scenario for using inline editor is offering users the possibility to edit content in its real location on a web page instead of doing it in a separate administration section.
{@img assets/img/editor-inline.png 774 Screenshot of an inline editor.}
To try it out online, check the {@link examples/builds/inline-editor inline editor example}. Jump to {@link builds/guides/quick-start#Inline-editor quick start} to start using it.
Balloon toolbar editor is very similar to inline editor. The difference between them is that the toolbar appears in a balloon next to the selection (when the selection is not empty):
{@img assets/img/editor-balloon-toolbar.png 779 Screenshot of a baloon toolbar editor.}
To try it out online, check the {@link examples/builds/balloon-toolbar-editor balloon toolbar editor example}. Jump to {@link builds/guides/quick-start#Balloon-toolbar-editor quick start} to start using it.
Every build comes with a default set of features and their default configuration. Although the builds try to fit many use cases, they may still need to be adjusted in some integrations. The following modifications are possible:
Read more in the {@link builds/guides/integration/configuration Configuration guide}.
If a build does not provide all the necessary features or you want to create a highly optimized build of the editor which will contain only the features that you require, you need to customize the build or create a brand new one. Check {@link builds/guides/development/custom-builds Custom builds} for details on how to change the default builds to match your preferences.
Each build was designed to satisfy as many use cases as possible. They differ in their UI, UX and features, and are based on the following approach:
Features like fonts, colors and alignment will be introduced in the future, when new types of builds will be introduced with the purpose of satisfying document editing scenarios.
Each of the builds fits several different use cases. Just think about any possible use for writing rich-text in applications.
The following are some common use cases:
The {@link framework/index CKEditor 5 Framework} should be used, instead of builds, in the following cases:
In the following cases CKEditor 4 should be used instead: