Cute Editor for ASP.NET

Cute Editor for ASP.NET Web Forms.

Add a WYSIWYG HTML editing control to an existing ASP.NET application. Evaluate formatting, image dialogs and the client and server APIs with your own content before deployment.

Live demos Download Pricing

Cute Editor for ASP.NET — The editor with the full toolbar enabled

Top features

Cross-browser, cross-platform

Evaluate the browser-based editor on the browsers and devices your application supports. Review the compatibility checklist before selecting a legacy build.
Standards-compliant output

Inspect the HTML or XHTML output using your headings, tables and pasted content. Apply your application's allowed-HTML policy when saving and displaying it.
Clean HTML from Microsoft Word

Paste from Word strips the word-processor markup before inserting the text, so pasted content stays clean.
Lightweight and fast loading

Numerous optimizations keep the editor clean, compact and extremely fast to load — while staying powerful.
Advanced file upload

Integrates the high-performance Ajax Uploader: multi-file selection with client-side size and type validation.
Store images in a database

Use SQL Server or an Access database as the file storage for uploaded images and documents.
Image insertion and thumbnails

Built-in thumbnail generator with paging and automatic image resizing, plus upload of new images from the dialog.
Fine-grained security

Assign pre-defined permission sets by group or individual, keeping administration functionality away from normal users.

Which ASP.NET editor does your project need?

This page covers the legacy Cute Editor server control and its .NET examples. ASP.NET Web Forms, ASP.NET MVC on .NET Framework and ASP.NET Core are different integration targets. A Web Forms control is not a drop-in component for a Core or Blazor application.

Maintain a Web Forms application

Start with the existing control, its sample pages and package-specific documentation. Confirm the target framework and assembly references in your project.

Try the .NET editing demo · Control documentation

Build with Core, MVC or Blazor

Compare the current RichTextEditor framework packages and their startup instructions. Plan content binding, uploads and saved HTML separately from the toolbar.

Compare framework packages · Read the .NET selection guide

Evaluate a complete editing workflow

Type and format: test headings, links, lists, tables and representative Word content in the demo.
Read and save: use the API for your installed version, then save through your authenticated application. Verify the record after a reload; a demo is not your database.
Check uploads: configure the handler, file limits, access rules and returned URLs. The browser dialog alone does not secure stored files.
Test real users' conditions: small screens, keyboard focus, right-to-left content, denied uploads and a failed save all belong in acceptance testing.

Use the HTML saving and upload checklist alongside the Cute Editor deployment requirements. For a quick Arabic or Hebrew writing task, the separate free online RTL editor does not require embedding a component.

ASP.NET editor questions

Is Cute Editor the same as the current JavaScript editor?

No. The legacy Cute Editor control and the current RichTextEditor packages have different APIs and setup steps. Use the documentation for the exact package you deploy.

Can I use this Web Forms control directly in ASP.NET Core?

No. Choose a package intended for your Core application and follow its sample project. Review the framework options before downloading.

Does adding an editor save content and secure uploads?

No. Your application must authenticate users, authorize changes, store HTML and enforce its HTML and file policies on the server. Follow the integration checklist.

Download

Cute Editor Home Online Demos Requirements Document Developer Guide Common Tasks Compare .NET editor options HTML save and upload checklist Advanced Topics Pricing Contact Us Customers