Important changes to Tiny Cloud pricing > Find out more

Cloud Deployment of Editor & Plugins

TinyMCE Cloud customers, you'll be up and running in less than 5 minutes.

Contribute to this page

TinyMCE Cloud is the easiest way to integrate TinyMCE and upgrade to our premium plugins.

You may use TinyMCE Cloud without an API key as mentioned in the General Configuration guide. However, to use our premium plugins or avoid the in-editor developer warning, you need to signup for an API key and update the script tag used to load the editor code into your application.

All TinyMCE Cloud accounts include a free, pre-configured cloud image proxy service. This is setup using the Image Tools plugin.

Integrating TinyMCE for the first time

Step 1: Embed the TinyMCE Cloud script tag into your webpage

To load TinyMCE for the very first time, you need to embed the TinyMCE editor code into your application. The code embedding is done by adding the following script tag into your app, or in the case of a web page the <head> of the page:

<script src="https://cdn.tiny.cloud/1/no-api-key/tinymce/4/tinymce.min.js?apiKey=your_API_key"></script>

Step 2: Load, customize and interact with TinyMCE

In addition to the advanced content creation solutions available in the Cloud offering, you have access to more than 40 open source plugins to enhance the editing experience. We have provided a range of simple examples and we encourage you to review our walkthrough documentation that will help you get started with TinyMCE.

Step 3: Specifying purchased TinyMCE plugins and toolbar/menu items

Lastly, you just need to extend your TinyMCE configuration to include any of the additional, advanced plugins (and associated toolbar/menu items) you’ve purchased. You will find enablement guides here:

Note: spellchecker_rpc_url is not required when enabling this plugin via TinyMCE Cloud.

Note:imagetools_cors_hosts and imagetools_proxy are not required to be configured when enabling this plugin via TinyMCE Cloud.

Note: Please note that after purchasing a plugin, it may take up to 30 minutes for the plugin to become available with your editor. You may also need to clear your browser's cache.

Step 4: Forward proxy configuration

If your company network has a forward proxy that controls access to the internet, please ensure that the following URLs are accessible via this proxy.

Important: Please ensure that the tiny-api-key and tinymce-api-key headers are retained while requesting the list of URLs above.

Step 5: Specifying a translation

If you wish to use a language other than English (US), please download a language pack and then specify its location with the language_url configuration option.

Migrating from a Self-hosted environment to TinyMCE Cloud

Step 1: Replace existing reference to tinymce.min.js

Migrating from a Self-hosted environment to the Cloud is a relatively straightforward process. Please remove your existing script tag that loads TinyMCE’s JavaScript (typically a reference to tinymce.min.js either hosted in your application or available via one our legacy CDNs). Now, replace this script tag with the following:

<script src="https://cdn.tiny.cloud/1/no-api-key/tinymce/4/tinymce.min.js?apiKey=your_API_key"></script>

Step 2: Update custom plugin paths

If you have any custom created plugins (or if you've modified any of the existing plugins), in order for these plugins to continue operating with your Cloud deployment, you'll need to reference these plugins via external_plugins rather than the regular plugins configuration element.

Step 3: Specify purchased TinyMCE plugins and toolbar buttons

Now, you just need to extend your TinyMCE configuration to include any additional plugins (and associated toolbar/menu items) you’ve purchased. You will find enablement guides here:

Note: spellchecker_rpc_url is not required when enabling this plugin via TinyMCE Cloud.

Note:imagetools_cors_hosts and imagetools_proxy are not required to be configured when enabling this plugin via TinyMCE Cloud.

Can't find what you're looking for? Let us know.

Except as otherwise noted, the content of this page is licensed under the Creative Commons BY-NC-SA 3.0 License, and code samples are licensed under the Apache 2.0 License.