Choose the edition for your stack
It is the same editor everywhere: the same toolbar, the same HTML output, the same AI Toolkit. What changes is the server side: how uploads, the image gallery and AI requests are handled in your language. Pick the row that matches your back end.
| Your stack | What you get | Where |
|---|---|---|
| JavaScript, React, Vue, Angular, Svelte, Next.js | The browser editor and npm package, with upload samples for Node, Express and Next.js route handlers. | Download here Overview on this site |
| TypeScript | Typed build of the editor for TypeScript projects. | ts.richtexteditor.com |
| ASP.NET Core (MVC, Razor Pages) | RichTextBox: a tag helper and .NET server code for uploads, the image gallery, HTML cleaning and AI resolvers, under your own authorization policies. | richtextbox.com Overview on this site |
| Blazor | The editor as a Blazor component, with demos and downloads for Blazor apps. | blazoreditor.com Overview on this site |
| ASP.NET Web Forms (.NET Framework) | A server control that replaces a TextBox in existing Web Forms pages, with upload handling. | richtexteditor.net |
| PHP | PHP integration with uploads, an image gallery and a file manager, plus guest, member and admin permissions. | phphtmleditor.com Overview on this site |
| Classic ASP | For maintaining existing Classic ASP applications. | asp.richtexteditor.com |
If you are not sure
Front end and back end differ
Choose by the server: that is where uploads and the gallery run. A React app with an ASP.NET Core API uses the React package in the browser and RichTextBox on the server.
Static site or headless CMS
Use the JavaScript edition. Write the upload endpoint in whatever your host runs; the guides include tested samples for several stacks.
Upgrading an old application
Web Forms and Classic ASP editions keep existing pages working. For a rewrite, plan the move to ASP.NET Core or a JavaScript front end. Migration guides
One license covers every stack
Every license tier includes the bindings for React, Vue, Angular, Svelte, Blazor, ASP.NET Core, Web Forms, PHP and Classic ASP. You don’t buy a separate product per framework. See pricing.
Still deciding?
Tell us your front end and back end, and we will point you to the right package and sample.