menu-title	Angular
meta-title	Using CKEditor 5 with Angular from CDN \| CKEditor 5 Documentation
meta-description	Install, integrate, and configure CKEditor 5 using the Angular component with CDN.
category	cloud
order	30

Integrating CKEditor 5 with Angular from CDN

Angular is a TypeScript-based, open-source, single-page web application framework. The CKEditor 5 component for Angular supports integrating different editor types.

{@snippet getting-started/use-builder}

Quick start

This guide assumes you already have an Angular project. To create such a project, you can use Angular CLI. Refer to the Angular documentation to learn more.

To use our Cloud CDN services, [create a free account](https://portal.ckeditor.com/checkout?plan=free). Learn more about {@link getting-started/licensing/license-key-and-activation license key activation}.

First, install the CKEditor 5 WYSIWYG editor component for Angular:

npm install @ckeditor/ckeditor5-angular

Angular is a TypeScript-first environment, so you may need to import TypeScript types for CKEditor. Depending on the plugins and features you use, you may also need to install the required open-source and premium packages:

npm install --save-dev ckeditor5 # Open-source plugin types.
npm install --save-dev ckeditor5-premium-features # Premium features plugin types.

In the below example, the loadCKEditorCloud helper is used to load the editor code and plugins from CDN. To use CKEditor 5 with CDN, you need to import the function and call it inside the ngOnInit lifecycle hook with the version provided in the configuration. To use premium plugins, set the premium property to true and provide your license key in the configuration. For more information about the loadCKEditorCloud helper, see the {@link getting-started/setup/loading-cdn-resources Loading CDN resources} guide.

// app.component.ts

import { Component } from '@angular/core';
import { CommonModule } from '@angular/common';
import { CKEditorModule, loadCKEditorCloud, CKEditorCloudResult } from '@ckeditor/ckeditor5-angular';
import type { ClassicEditor, EditorConfig } from 'https://cdn.ckeditor.com/typings/ckeditor5.d.ts';

@Component( {
	selector: 'app-root',
	templateUrl: './app.component.html',
	styleUrls: ['./app.component.css'],
	imports: [ CommonModule, CKEditorModule ],
	standalone: true
} )
export class AppComponent {
	public Editor: typeof ClassicEditor | null = null;

	public config: EditorConfig | null = null;

	public ngOnInit(): void {
		loadCKEditorCloud( {
			version: '{@var ckeditor5-version}',
			premium: true
		} ).then( this._setupEditor.bind( this ) );
	}

	private _setupEditor ( cloud: CKEditorCloudResult<{ version: '{@var ckeditor5-version}', premium: true }> ) {
		const {
			ClassicEditor,
			Essentials,
			Paragraph,
			Bold,
			Italic
		} = cloud.CKEditor;

		const { FormatPainter } = cloud.CKEditorPremiumFeatures;

		this.Editor = ClassicEditor;
		this.config = {
			licenseKey: '<YOUR_LICENSE_KEY>',
			plugins: [ Essentials, Paragraph, Bold, Italic, FormatPainter ],
			toolbar: [ 'undo', 'redo', '|', 'bold', 'italic', '|', 'formatPainter' ]
		};
	}
}

In the example above, the EditorConfig type is imported from the https://cdn.ckeditor.com/typings/ckeditor5.d.ts package, while the editor itself loads from the CDN. Note that https://cdn.ckeditor.com/typings/ckeditor5.d.ts is not an actual URL to the CKEditor 5 typings file but a synthetic TypeScript module providing type definitions for the editor. The ckeditor5 or ckeditor5-premium-features packages supply the actual types, which depend on the @ckeditor/ckeditor5-angular package.

Finally, use the <ckeditor> tag in the template to run the rich text editor. The usage is the same regardless of the plugin configuration.

<!-- app.component.html -->

<ckeditor
	*ngIf="( Editor && config )"
	data="<p>Hello, world!</p>"
	[editor]="Editor"
	[config]="config"
>
</ckeditor>

Supported `@Input` properties

The following @Input properties are supported by the CKEditor 5 rich text editor component for Angular:

`editor` (required)

The {@link getting-started/setup/editor-lifecycle Editor} which provides the static {@link module:core/editor/editor~Editor.create create()} method to create an instance of the editor:

<ckeditor [editor]="Editor"></ckeditor>

`config`

The {@link module:core/editor/editorconfig~EditorConfig configuration} of the editor:

<ckeditor [config]="{ toolbar: [ 'heading', '|', 'bold', 'italic' ] }"></ckeditor>

`data`

The initial data of the editor. It can be a static value:

<ckeditor data="<p>Hello, world!</p>"></ckeditor>

or a shared parent component's property

@Component( {
	// ...
} )
export class MyComponent {
	public editorData;

	private _setupEditor( cloud ) {
		this.editorData = '<p>Hello, world!</p>';
	}
	// ...
}

<ckeditor [data]="editorData"></ckeditor>

`tagName`

The tag name of the HTML element on which the rich text editor will be created.

The default tag is <div>.

<ckeditor tagName="textarea"></ckeditor>

`disabled`

Controls the editor's {@link module:core/editor/editor~Editor#isReadOnly read–only} state:

@Component( {
	// ...
} )
export class MyComponent {
	public isDisabled;
	// ...
	private _setupEditor( cloud ) {
		this.isDisabled = false;
	}
	toggleDisabled() {
		this.isDisabled = !this.isDisabled;
	}
}

<ckeditor [disabled]="isDisabled"></ckeditor>

<button (click)="toggleDisabled()">
	{{ isDisabled ? 'Enable editor' : 'Disable editor' }}
</button>

`watchdog`

An instance of the {@link module:watchdog/contextwatchdog~ContextWatchdog ContextWatchdog} class that is responsible for providing the same context to multiple editor instances and restarting the whole structure in case of crashes.

import { loadCKEditorCloud } from '@ckeditor/ckeditor5-angular';

@Component( {
	// ...
} )
export class MyComponent {
	public editor;
	public watchdog: any;
	public ready;

	ngOnInit() {
		loadCKEditorCloud( {
			version: '{@var ckeditor5-version}',
		} ).then( this._setupEditor.bind( this ) );
	}

	private _setupEditor( cloud ) {
		const {
			ClassicEditor,
			ContextWatchdog,
			Context
		} = cloud.CKEditor;

		const contextConfig = {
			// Your context configuration.
		};

		this.Editor = ClassicEditor;
		this.ready = false;

		this.watchdog = new ContextWatchdog( Context );

		this.watchdog.create( contextConfig )
			.then( () => {
				this.ready = true;
			} );
	}
}

<div *ngIf="ready">
	<ckeditor [watchdog]="watchdog"></ckeditor>
	<ckeditor [watchdog]="watchdog"></ckeditor>
	<ckeditor [watchdog]="watchdog"></ckeditor>
</div>

`editorWatchdogConfig`

If the watchdog property is not used, {@link module:watchdog/editorwatchdog~~EditorWatchdog EditorWatchdog} will be used by default. editorWatchdogConfig property allows for passing a {@link module:watchdog/watchdog~~WatchdogConfig config} to that watchdog.

@Component( {
	// ...
} )
export class MyComponent {
	public myWatchdogConfig;

	private _setupEditor( cloud ) {
		this.myWatchdogConfig = {
			crashNumberLimit: 5,
			// ...
		};
	}
	// ...
}

<ckeditor [editorWatchdogConfig]="myWatchdogConfig"></ckeditor>

`disableTwoWayDataBinding`

Allows disabling the two-way data binding mechanism. The default value is false.

The reason for the introduction of this option is performance issues in large documents. By default, while using the ngModel directive, whenever the editor's data is changed, the component must synchronize the data between the editor instance and the connected property. This results in calling the {@link module:core/editor/editor~Editor#getData editor.getData()} function, which causes a massive slowdown while typing in large documents.

This option allows the integrator to disable the default behavior and only call the {@link module:core/editor/editor~Editor#getData editor.getData()} method on demand, which prevents the slowdowns. You can read more in the relevant issue.

Supported `@Output` properties

The following @Output properties are supported by the CKEditor 5 rich text editor component for Angular:

`ready`

Fired when the editor is ready. It corresponds with the editor#ready event. It is fired with the editor instance.

Note that this method might be called multiple times. Apart from initialization, it is also called whenever the editor is restarted after a crash. Do not keep the reference to the editor instance internally, because it will change in case of a restart. Instead, you should use the watchdog.editor property.

`change`

Fired when the content of the editor has changed. It corresponds with the {@link module:engine/model/document~ModelDocument#event:change:data editor.model.document#change:data} event. It is fired with an object containing the editor and the CKEditor 5 change:data event object.

<ckeditor [editor]="Editor" (change)="onChange($event)"></ckeditor>

import { ClassicEditor } from 'ckeditor5';
import { ChangeEvent } from '@ckeditor/ckeditor5-angular/ckeditor.component';

@Component( {
	// ...
} )
export class MyComponent {
	public Editor;

	private _setupEditor( cloud ) {
		const {
			ClassicEditor
		} = cloud.CKEditor;

		this.Editor = ClassicEditor;
	}

	public onChange( { editor }: ChangeEvent ) {
		const data = editor.getData();

		console.log( data );
	}
	// ...
}

`blur`

Fired when the editing view of the editor is blurred. It corresponds with the {@link module:engine/view/document~ViewDocument#event:blur editor.editing.view.document#blur} event. It is fired with an object containing the editor and the CKEditor 5 blur event data.

`focus`

Fired when the editing view of the editor is focused. It corresponds with the {@link module:engine/view/document~ViewDocument#event:focus editor.editing.view.document#focus} event. It is fired with an object containing the editor and the CKEditor 5 focus event data.

`error`

Fired when the editor crashes. Once the editor has crashed, the internal watchdog mechanism restarts the editor and fires the ready event.

Prior to ckeditor5-angular `v7.0.1`, this event was not fired for crashes during the editor initialization.

Integration with `ngModel`

The component implements the ControlValueAccessor interface and works with the ngModel. Here is how to use it:

Create some model in your component to share with the editor:

@Component( {
	// ...
} )
export class MyComponent {
	public model;

	private _setupEditor( cloud ) {
		this.model = {
			editorData: '<p>Hello, world!</p>'
		};
	}
	// ...
}

Use the model in the template to enable a two–way data binding:

<ckeditor [(ngModel)]="model.editorData" [editor]="Editor"></ckeditor>

Styling

The CKEditor 5 rich text editor component for Angular can be styled using the component style sheet or using a global style sheet. See how to set the CKEditor 5 component's height using these two approaches.

Setting the height via the component style sheet

First, create a (S)CSS file in the parent component's directory and style the given editor's part preceded by the :host and ::ng-deep pseudo selectors:

/* src/app/app.component.css */

:host ::ng-deep .ck-editor__editable_inline {
	min-height: 500px;
}

Then, in the parent component, add the relative path to the above style sheet:

/* src/app/app.component.ts */

@Component( {
	// ...
	styleUrls: [ './app.component.css' ]
} )

Setting the height via a global style sheet

To style the component using a global style sheet, first, create it:

/* src/styles.css */

.ck-editor__editable_inline {
	min-height: 500px;
}

Then, add it to the angular.json configuration file:

"architect": {
	"build": {
		"options": {
			"styles": [
				{ "input": "src/styles.css" }
			]
		}
	}
}

Setting the placeholder

To display {@link features/editor-placeholder the placeholder} in the main editable element, set the placeholder field in the CKEditor 5 rich text editor component configuration:

@Component( {
	// ...
} )
export class MyComponent {
	public config;

	private _setupEditor( cloud ) {
		// ...
		this.config = {
			placeholder: 'Type the content here!'
		}
	}

}

Accessing the editor instance

The CKEditor 5 rich text editor component provides all the functionality needed for most use cases. When access to the full CKEditor 5 API is needed, you can get the editor instance with an additional step.

To do this, create a template reference variable #editor pointing to the <ckeditor> component:

<ckeditor #editor [editor]="Editor"></ckeditor>

Then get the <ckeditor> component using a property decorated by @ViewChild( 'editor' ) and access the editor instance when needed:

@Component()
export class MyComponent {
	@ViewChild( 'editor' ) editorComponent: CKEditorComponent;

	public getEditor() {
		// Warning: This may return "undefined" if the editor is hidden behind the `*ngIf` directive or
		// if the editor is not fully initialised yet.
		return this.editorComponent.editorInstance;
	}
}

The editor creation is asynchronous, so the `editorInstance` will not be available until the editor is created. If you want to make changes to an editor that has just been created, a better option would be getting the CKEditor 5 instance on the [`ready`](#ready) event.

How to?

Using the Document editor type

If you want to use the {@link framework/document-editor document (decoupled) editor}, you need to {@link module:editor-decoupled/decouplededitor~DecoupledEditor.create add the toolbar to the DOM manually}:

// app.component.ts

import { Component } from '@angular/core';
import { CommonModule } from '@angular/common';
import { CKEditorCloudResult, CKEditorModule, loadCKEditorCloud } from '@ckeditor/ckeditor5-angular';
import { DecoupledEditor, EditorConfig } from 'https://cdn.ckeditor.com/typings/ckeditor5.d.ts';

@Component( {
	selector: 'app-root',
	templateUrl: './app.component.html',
	styleUrls: [ './app.component.css' ],
	imports: [ CommonModule, CKEditorModule ],
	standalone: true
} )
export class AppComponent {
	title = 'angular';

	public Editor: typeof DecoupledEditor | null = null;

	public config: EditorConfig | null = null;

	public ngOnInit(): void {
		loadCKEditorCloud( {
			version: '{@var ckeditor5-version}'
		} ).then( this._setupEditor.bind( this ) );
	}

	private _setupEditor( cloud: CKEditorCloudResult<{ version: '{@var ckeditor5-version}'}>) {
		const {
			DecoupledEditor,
			Essentials,
			Paragraph,
			Bold,
			Italic
		} = cloud.CKEditor;

		this.Editor = DecoupledEditor;
		this.config = {
			licenseKey: '<YOUR_LICENSE_KEY>',
			plugins: [ Essentials, Paragraph, Bold, Italic ],
			toolbar: [ 'undo', 'redo', '|', 'bold', 'italic' ]
		};
	}

	public onReady( editor: DecoupledEditor ) {
		const element = editor.ui.getEditableElement()!;
		const parent = element.parentElement!;

		parent.insertBefore(
			editor.ui.view.toolbar.element!,
			element
		);
	}
}

And then, link the method in the template:

<!-- app.component.html -->

<ckeditor
  *ngIf="(Editor && config)"
  data="<p>Hello, world!</p>"
  [editor]="Editor"
  [config]="config"
  (ready)="onReady($event)"
>
</ckeditor>

Using the editor with collaboration plugins

We provide a few ready-to-use integrations featuring collaborative editing in Angular applications:

It is not mandatory to build applications on top of the above samples; however, they should help you get started.

Localization

CKEditor 5 supports {@link getting-started/setup/ui-language multiple UI languages}, and so does the official Angular component. To translate the editor, pass the languages you need into the translations array inside the configuration of the loadCKEditorCloud function.

import { Component } from '@angular/core';
import { CommonModule } from '@angular/common';
import { CKEditorModule, loadCKEditorCloud, CKEditorCloudResult } from '@ckeditor/ckeditor5-angular';
import { ClassicEditor, EditorConfig } from 'https://cdn.ckeditor.com/typings/ckeditor5.d.ts';

@Component( {
	selector: 'app-root',
	templateUrl: './app.component.html',
	styleUrls: ['./app.component.css'],
	imports: [ CommonModule, CKEditorModule ],
	standalone: true
} )
export class AppComponent {
	public Editor: typeof ClassicEditor | null = null;

	public config: EditorConfig | null = null;

	public ngOnInit(): void {
		loadCKEditorCloud( {
			version: '{@var ckeditor5-version}',
			translations: [ 'es' ]
		} ).then( this._setupEditor.bind( this ) );
	}

	private _setupEditor ( cloud: CKEditorCloudResult<{ version: '{@var ckeditor5-version}'}> ) {
		const {
			ClassicEditor,
			Paragraph,
			Essentials,
			Bold,
			Italic
		} = cloud.CKEditor;

		this.Editor = ClassicEditor;
		this.config = {
			licenseKey: '<YOUR_LICENSE_KEY>',
			plugins: [ Essentials, Bold, Italic, Paragraph ],
			toolbar: [ 'undo', 'redo', '|', 'bold', 'italic' ]
		};
	}
}

Supported Angular versions

Starting from version 6.0.0 of this package, you can use native type definitions provided by CKEditor 5. Check the details about {@link getting-started/setup/typescript-support TypeScript support}.

Because of the breaking changes in the Angular library output format, the @ckeditor/ckeditor5-angular package is released in the following versions to support various Angular ecosystems:

CKEditor 5 Angular component version	Angular version	Details
Actively supported versions
`^9`	`16+`	Migration to TypeScript 5. Declaration files are not backward compatible. Requires CKEditor 5 in version 43 or higher.
Past releases (no longer maintained)
`^8`	`13+`	Requires CKEditor 5 in version 42 or higher.
`^7`	`13+`	Changes in peer dependencies (issue). Requires CKEditor 5 in version 37 or higher.
`^6`	`13+`	Requires CKEditor 5 in version 37 or higher.
`^5`	`13+`	Requires Angular in version 13+ or higher. Lower versions are no longer maintained.
`^5`	`13+`	Requires Angular in version 13+ or higher. Lower versions are no longer maintained.
`^4`	`9.1+`	Requires CKEditor 5 in version 34 or higher.
`^3`	`9.1+`	Requires Node.js in version 14 or higher.
`^2`	`9.1+`	Migration to TypeScript 4. Declaration files are not backward compatible.
`^1`	`5.x - 8.x`	Angular versions no longer maintained.

All available Angular versions are listed on npm, where they can be pulled from.

Contributing and reporting issues

The source code of the CKEditor 5 rich text editor component for Angular is available on GitHub at https://github.com/ckeditor/ckeditor5-angular.

Next steps

See how to manipulate the editor's data in the {@link getting-started/setup/getting-and-setting-data Getting and setting data} guide.
Refer to further guides in the {@link getting-started/setup/configuration setup section} to see how to customize your editor further.
Check the {@link features/index features category} to learn more about individual features.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Integrating CKEditor 5 with Angular from CDN

Quick start

Supported `@Input` properties

`editor` (required)

`config`

`data`

`tagName`

`disabled`

`watchdog`

`editorWatchdogConfig`

`disableTwoWayDataBinding`

Supported `@Output` properties

`ready`

`change`

`blur`

`focus`

`error`

Integration with `ngModel`

Styling

Setting the height via the component style sheet

Setting the height via a global style sheet

Setting the placeholder

Accessing the editor instance

How to?

Using the Document editor type

Using the editor with collaboration plugins

Localization

Supported Angular versions

Contributing and reporting issues

Next steps

Uh oh!

FilesExpand file tree

angular.md

Latest commit

History

angular.md

File metadata and controls

Integrating CKEditor 5 with Angular from CDN

Quick start

Supported @Input properties

editor (required)

config

data

tagName

disabled

watchdog

editorWatchdogConfig

disableTwoWayDataBinding

Supported @Output properties

ready

change

blur

focus

error

Integration with ngModel

Styling

Setting the height via the component style sheet

Setting the height via a global style sheet

Setting the placeholder

Accessing the editor instance

How to?

Using the Document editor type

Using the editor with collaboration plugins

Localization

Supported Angular versions

Contributing and reporting issues

Next steps

Supported `@Input` properties

`editor` (required)

`config`

`data`

`tagName`

`disabled`

`watchdog`

`editorWatchdogConfig`

`disableTwoWayDataBinding`

Supported `@Output` properties

`ready`

`change`

`blur`

`focus`

`error`

Integration with `ngModel`