You can install a self-hosted WebSpellChecker Server on:

  • A dedicated server
  • Virtual machine (you can enable VMWare virtualization when installing WebSpellChecker)
  • Docker container

Or using one of the cloud service providers.

Here are the minimum hardware requirements for WebSpellChecker Server installation:

ItemsMinimum valueComments

Minimum 350 MB of disk space is required for WebSpellChecker installation package, including AppServer, Engines, and web components.

Additional space can be required for the following components: 

  • Up to 2 MB for all personal user dictionaries in .../UserDictionaries and up to 10 MB for global custom dictionaries in .../CustomDictionaries directory.
  • Up to 15 MB for the AppServer log files to be saved in the AppServer/Logs directory. Once a log file size reaches 10 MB, a new log file will be created. 
  • Web Server logs, for example, access logs of Apache HTTP Server. Such logs can require a significant amount of disk space as it keeps the records of all served requests. It is your responsibility to monitor and control space consumption by access logs.
  • Up to 90 MB of memory if you decide to enable detailed logging of one of the WebSpellChecker components (namely, for the SSRV FastCGI component). However, this type of logging is turned off by default. 
  • Additional space for usage statistics logs if you enable them. For details, refer to the Enabling collection of usage statistics in logs guide.  

Sometimes you may need to allocate even more space depending on WebSpellChecker Server environment needs, for example, if the number of your language dictionaries includes 100+ languages.

Make sure you regularly verify the amount of disk space consumed by your logs and allocate more space if necessary. 


At least 200 MB of memory is required for spell check, grammar check engines, and cache functioning, if you are referring to WebSpellChecker Application Server (AppServer). Also, consider the following RAM requirements:

  • 50 MB for a spelling check engine including 16 default languages (English language dictionary is actively used).
  • 128 MB for the English grammar check engine, plus 512 MB if other languages (from the list of 14 default ones) support is enabled. You also need to consider memory usage for grammar checking if you are using all default languages where grammar checking is supported.
  • 10 MB for cache enabled on Server (for 10 000 suggestions). The rough calculation here is 1 misspelling and its suggestions equals 100 bytes. The more misspellings and suggestions to be added to the cache the more RAM will be needed.

The numbers in the list above may change depending on your custom environment setup and usage. 

CPU2 CPU Cores

Please note that these are minimum installation requirements which change and vary depending on:

  • Number of end-users who will be using WebSpellChecker features or proofreading;
  • Amount of text they need to be proofread;
  • Type of language as well as the size of its language;
  • Percent of text errors.

The list of supported providers is presented in table below.

If you want to use AWS EC2 instance, you can choose a smaller instance such as t3.medium with 2 CPUs, 4 GB of memory or a server with similar characteristics. We host and maintain our WebSpellChecker Cloud version on Amazon Web Services (AWS) and use a set of m5.large EC2 instances under the load balancer for our application’s workload which is up to 50,000 requests per minute.

If you don’t have a dedicated hardware, you can try using WebSpellChecker Cloud version. No software installation and configuration is required and you can migrate to your own server any time later.