How to Install MongoDB: A Practical Guide for 2026

MongoDB is a free, open-source NoSQL database that stores information in flexible JSON-like documents rather than the fixed tables and rows you’d find in traditional databases. This design suits modern web applications that need to handle diverse data types, scale across multiple servers or work with information that changes structure over time. Think of MySQL as a filing cabinet with fixed drawers and folders where every item must fit the same template. MongoDB works more like a flexible storage system where each item can contain different fields and nested data without requiring schema changes.

The practical difference becomes clear when you’re building e-commerce catalogues with products that have varying attributes, user profiles where different customers provide different information, content management systems handling multiple content types or real-time analytics dashboards. MongoDB handles these scenarios naturally because you can add new fields to documents without restructuring your entire database or running complex migration scripts.

Most simple WordPress or Joomla sites don’t need MongoDB. The MySQL database your shared hosting provides handles typical content management perfectly well. MongoDB becomes relevant when you’re developing custom applications, working with Node.js and Express frameworks or need horizontal scaling across multiple servers as your traffic grows. Providers like 123 Reg and Heart Internet offer MySQL on their shared hosting plans, but MongoDB requires VPS hosting from providers like Hostinger UK, Fasthosts or DigitalOcean where you have the server access and resources to install it yourself.

Before you start installation, verify your system meets the minimum specifications for MongoDB 8.0, which is the current stable version in 2026. You’ll need at least 2 GB of RAM for reliable operation, though 1 GB is the absolute minimum for testing environments. MongoDB requires a 64-bit processor and approximately 1 GB of free disk space for the installation files, plus whatever storage your databases will consume. Systems running 32-bit operating systems are no longer supported.

Supported operating systems include Windows 10, Windows 11 and Windows Server 2016 or later (all 64-bit versions). On macOS, you’ll need Big Sur (version 11) or later. Linux users should run Ubuntu 20.04 LTS, 22.04 LTS or 24.04 LTS, or Debian 10, 11 or 12. If you’re installing on a VPS, verify your hosting plan provides sufficient RAM because undersized servers cause MongoDB to crash or perform poorly under load.

You’ll need administrator privileges on Windows or root access on Linux to install MongoDB properly. This means shared hosting customers cannot install it regardless of their plan. VPS or dedicated server access is essential because MongoDB installation involves creating system services, modifying system directories and configuring network ports. Check that port 27017 (MongoDB’s default) isn’t already occupied by another service on your server.

Windows installation involves downloading the official installer, running the setup wizard, configuring MongoDB as a system service and setting up your environment variables so you can run MongoDB commands from any command prompt. The process takes about 10 to 15 minutes on a typical system with a decent internet connection.

Visit the MongoDB Download Centre at mongodb.com/try/download/community and select “Community Server” from the product options. Choose “Windows” as your platform and select the latest version, which is 8.0 as of 2026. You’ll see options for “Current” release (latest features) or “LTS” (Long Term Support). Choose LTS for production environments where stability matters more than cutting-edge features, or Current if you’re developing and want the newest capabilities.

Download the MSI package, which is approximately 300 MB. The installer includes MongoDB Compass, a graphical database management tool that’s helpful for visualising your data and running queries without command-line work. The MSI format provides a standard Windows installation wizard that handles most configuration automatically.

Double-click the downloaded MSI file to launch the installer. You’ll need to accept the licence agreement on the first screen. When you reach the setup type selection, choose “Complete” for a standard installation that includes all components and uses default paths. The “Custom” option lets you select specific components or change the installation directory, but most users don’t need this flexibility.

The default installation path is C:Program FilesMongoDBServer8.0, which works well for most scenarios. The installer requires administrator privileges, so Windows will prompt you to confirm elevated access. Click through the setup screens, accepting the defaults unless you have specific requirements for custom paths or component selection.

During installation, you’ll see an option labelled “Install MongoD as a Service”. Tick this box to have MongoDB start automatically whenever Windows boots. This configuration suits development servers or applications that need MongoDB running constantly. The installer sets up a Windows service named “MongoDB” that you can manage through the Services control panel.

Default service settings include a data directory at C:Program FilesMongoDBServer8.0data and a log directory at C:Program FilesMongoDBServer8.0log. These paths work for most users, but if you need to store databases on a different drive (perhaps because your C: drive has limited space), you can change these paths during Custom setup. If you skip the service configuration, you’ll need to start MongoDB manually each time by opening a command prompt and running the mongod command.

Adding MongoDB to your system PATH allows you to run mongo and mongod commands from any command prompt without typing the full path to the executable files. Open System Properties by right-clicking “This PC” and selecting Properties, then click “Advanced system settings” and the “Environment Variables” button.

Under System variables, find the “Path” variable and click Edit. Add a new entry: C:Program FilesMongoDBServer8.0bin. Click OK on all dialogue boxes to save your changes. To verify this worked, open a new Command Prompt window (important: it must be a new window opened after the PATH change) and type mongod –version. You should see version information displayed, confirming that Windows can now find the MongoDB executables.

The most common Windows installation error is “Data directory C:/data/db/ not found”. MongoDB expects a default data directory at C:datadb but the installer doesn’t always create it automatically in custom setups or when you skip the service configuration. The database server cannot start without a valid data directory to store information.

To fix this, open Command Prompt as administrator (right-click Command Prompt and select “Run as administrator”) and run mkdir C:datadb. This creates both the data and db folders in one command. Alternatively, specify a custom data directory when starting MongoDB by running mongod –dbpath “C:yourcustompath”, replacing the path with wherever you want to store your databases. Service installations with configured data paths avoid this issue because the installer creates the necessary directories during setup.

Homebrew simplifies MongoDB installation on macOS by handling downloads, dependencies and configuration automatically through command-line package management. This approach is cleaner and easier to maintain than manual installation from ZIP archives.

If you don’t already have Homebrew installed, visit brew.sh and follow the installation instructions there first. Once Homebrew is ready, open Terminal and run brew tap mongodb/brew to add MongoDB’s official Homebrew repository. This command tells Homebrew where to find MongoDB packages that aren’t in the default repository.

Next, run brew install mongodb-community@8.0 to install MongoDB 8.0 Community Edition. Homebrew downloads the necessary files (approximately 300 MB), installs MongoDB binaries, creates configuration files and sets up default data and log directories automatically. The installation typically takes 2 to 5 minutes depending on your internet connection speed. You’ll see progress messages in Terminal as Homebrew works through the installation steps.

To run MongoDB as a background service that starts automatically when you log in, use brew services start mongodb-community. This command launches MongoDB and configures macOS to restart it automatically if it crashes or when you reboot your computer. Verify the service is running by typing brew services list, which displays all Homebrew services and their status. You should see mongodb-community listed as “started”.

If you prefer to run MongoDB manually without automatic startup (useful during development when you don’t need the database running all the time), use mongod –config /opt/homebrew/etc/mongod.conf instead. This starts MongoDB in your current Terminal session and stops when you close the window or press Control+C. The default data directory is /opt/homebrew/var/mongodb and logs are written to /opt/homebrew/var/log/mongodb/mongo.log.

Open a new Terminal window and run mongosh to launch the MongoDB Shell. If installation succeeded, you’ll connect to the default database and see a prompt like test>. This confirms that MongoDB server is running and accepting connections. Type db.version() and press Enter to display the installed MongoDB version, which should show 8.0.x.

If you see an error saying mongosh isn’t recognised, you may need to install MongoDB Shell separately because it’s been distributed as a standalone package since MongoDB 5.0. Run brew install mongosh to add the shell tool. Once installed, mongosh should connect successfully to your running MongoDB server.

Most UK VPS hosting runs Ubuntu or Debian Linux, making this the primary production environment for MongoDB in web hosting contexts. Installation involves adding MongoDB’s official package repository, importing security keys, installing packages through your system’s package manager and configuring MongoDB as a system service.

Ubuntu and Debian default repositories often contain outdated MongoDB versions, so you’ll add MongoDB’s official repository to get the latest stable release. Start by importing the GPG key that verifies package authenticity. On Ubuntu 24.04, run curl -fsSL https://www.mongodb.org/static/pgp/server-8.0.asc | sudo gpg -o /usr/share/keyrings/mongodb-server-8.0.gpg –dearmor. This downloads MongoDB’s public key and stores it in a format your system can use for package verification.

Next, create the repository list file by running echo “deb [ arch=amd64,arm64 signed-by=/usr/share/keyrings/mongodb-server-8.0.gpg ] https://repo.mongodb.org/apt/ubuntu noble/mongodb-org/8.0 multiverse” | sudo tee /etc/apt/sources.list.d/mongodb-org-8.0.list. The word “noble” is Ubuntu 24.04’s codename. If you’re running a different version, check your Ubuntu release with lsb_release -a and use the appropriate codename: “jammy” for 22.04 or “focal” for 20.04.

Debian users need different repository URLs. Replace “ubuntu” with “debian” in the repository URL and use “bookworm” for Debian 12 or “bullseye” for Debian 11. The GPG key import process remains the same across distributions.

Update your package index to include the newly added MongoDB repository by running sudo apt update. This refreshes the list of available packages so your system knows about MongoDB 8.0. Then install MongoDB with sudo apt install -y mongodb-org. The -y flag automatically confirms installation prompts.

This command installs several packages: mongodb-org-server (the database server itself), mongodb-org-mongos (the sharding router for distributed deployments), mongodb-org-shell (the legacy command-line shell) and mongodb-org-tools (utilities for importing, exporting and managing databases). The total download is approximately 500 MB and installation typically takes 2 to 5 minutes on a standard VPS.

If you’re setting up a production server and want to prevent automatic MongoDB updates during system upgrades, pin the version by running echo “mongodb-org hold” | sudo dpkg –set-selections. This keeps MongoDB at the current version until you explicitly choose to upgrade, preventing unexpected changes that might affect your applications.

Ubuntu and Debian use systemd for service management. Start MongoDB with sudo systemctl start mongod, which launches the database server immediately. Check that it’s running properly by typing sudo systemctl status mongod. You should see “active (running)” in green text, along with recent log entries showing successful startup.

To make MongoDB start automatically when your server boots, run sudo systemctl enable mongod. This creates the necessary system links so MongoDB launches during the boot sequence. If you need to restart MongoDB after configuration changes, use sudo systemctl restart mongod. These systemctl commands work consistently across modern Linux distributions.

MongoDB stores data in /var/lib/mongodb by default, writes logs to /var/log/mongodb/mongod.log and reads configuration from /etc/mongod.conf. If MongoDB fails to start, check the log file for error messages. Common startup failures include port 27017 already being used by another service, insufficient disk space or permission problems on the data directory.

Verify the installation by checking the MongoDB version with mongod –version. You should see version 8.0.x displayed along with build information. Connect to the database by running mongosh (or mongo if you’re using the older shell). A successful connection displays the MongoDB shell prompt, confirming the server is running and accepting connections.

Run a test command to verify connectivity: db.runCommand({ connectionStatus: 1 }). This returns a document showing your connection status and authentication information. By default, MongoDB listens only on localhost (127.0.0.1), meaning it accepts connections only from the same server. If you need remote access from other servers or your local development machine, you’ll need to modify the bindIp setting in /etc/mongod.conf and configure your firewall appropriately. Remote access introduces security considerations beyond basic installation, so research authentication and network security before exposing MongoDB to external connections.

If you’re working on a corporate machine or shared computer where you don’t have administrator privileges, you can still run MongoDB for development purposes using a portable installation approach. This method doesn’t install MongoDB as a Windows Service and requires manual startup each time, but it works without elevated permissions.

Visit the MongoDB download page and select the ZIP archive instead of the MSI installer. Extract the ZIP file to a location where you have write permissions, such as C:UsersYourNamemongodb. Create two subdirectories inside this folder: one called “data” and another called “log”. These will store your databases and MongoDB’s operational logs.

To start MongoDB, open Command Prompt, navigate to your MongoDB folder with cd C:UsersYourNamemongodbbin, then run mongod –dbpath “C:UsersYourNamemongodbdata” –logpath “C:UsersYourNamemongodblogmongod.log”. The –dbpath flag tells MongoDB where to store databases and –logpath specifies where to write logs. MongoDB starts and runs in the current Command Prompt window.

This approach has limitations. MongoDB won’t start automatically when Windows boots, so you must run the command each time you need the database. You’ll need to keep the Command Prompt window open whilst MongoDB runs, or use start /b mongod … to run it in the background. This setup suits development and testing but isn’t recommended for production servers or applications that need MongoDB running continuously. For proper production deployment, you’ll need VPS hosting where you have full administrative access.

Installation doesn’t always proceed smoothly, particularly when system configurations vary or prerequisites aren’t met. Common issues include missing data directories, port conflicts, permission problems and repository configuration errors. Each has straightforward solutions once you understand the underlying cause.

The “Data directory C:/data/db/ not found” error appears when MongoDB tries to start but cannot locate its default data storage location. This happens if you didn’t configure MongoDB as a Windows Service during installation or if you’re running MongoDB manually without specifying a data directory. MongoDB cannot start without a valid location to store database files.

Fix this by opening Command Prompt as administrator and running mkdir C:datadb to create the expected directory structure. Alternatively, specify a custom data directory each time you start MongoDB: mongod –dbpath “C:yourcustompath”.

This error means another process is already listening on port 27017, which is MongoDB’s default port. The most common cause is an existing MongoDB instance that’s already running, either as a Windows Service or from a previous manual startup that you forgot to stop. Less commonly, another application might be using this port.

On Linux, check if MongoDB is running with sudo systemctl status mongod. If it shows “active”, stop it with sudo systemctl stop mongod before trying to start a new instance. On Windows, open Task Manager, look for mongod.exe in the Processes tab and end the task if it’s running. If you need to run multiple MongoDB instances simultaneously (for testing different configurations), start the second instance on a different port: mongod –port 27018. Remember that when you change the port, you must specify it when connecting: mongosh –port 27018.

Permission denied errors on Linux occur when the mongodb user (which the MongoDB service runs as) doesn’t have write access to the data directory, typically /var/lib/mongodb. This can happen if you manually created the directory with incorrect ownership or if disk permissions were changed by another process or system update.

Fix this by ensuring the mongodb user owns the data directory: sudo chown -R mongodb:mongodb /var/lib/mongodb. The -R flag applies ownership recursively to all files and subdirectories. Then verify the directory has appropriate permissions: sudo chmod 755 /var/lib/mongodb. This gives the owner (mongodb user) full read, write and execute permissions whilst allowing others to read and navigate the directory. After correcting permissions, restart MongoDB with sudo systemctl restart mongod.

GPG key import errors prevent you from adding MongoDB’s repository because your system cannot verify package authenticity without the public key. Common causes include network connectivity issues, incorrect key URLs or missing the gnupg package that handles key management.

First, ensure gnupg is installed: sudo apt install gnupg. This package handles GPG key operations on Debian and Ubuntu systems. Verify you’re using the correct GPG key URL for MongoDB 8.0: https://www.mongodb.org/static/pgp/server-8.0.asc. MongoDB changes key URLs with major versions, so outdated installation guides might reference wrong URLs. If curl isn’t working, try wget as an alternative: wget -qO – https://www.mongodb.org/static/pgp/server-8.0.asc | sudo gpg -o /usr/share/keyrings/mongodb-server-8.0.gpg –dearmor. Check MongoDB’s official documentation if you continue having issues, as key distribution methods occasionally change.

Installation is just the first step. Several critical post-installation tasks secure your database and prepare it for actual use. Authentication configuration is particularly important because skipping it leaves your MongoDB server vulnerable to unauthorised access.

Enable authentication immediately, especially on production servers. By default, MongoDB has no access control, meaning anyone who can connect to port 27017 has full database access. Create an admin user by connecting with mongosh, switching to the admin database with use admin, then running db.createUser({ user: “admin”, pwd: “yourSecurePassword”, roles: [“root”] }). Edit your configuration file (/etc/mongod.conf on Linux or C:Program FilesMongoDBServer8.0binmongod.cfg on Windows) and add security: authorization: enabled under the security section. Restart MongoDB for changes to take effect.

Configure your firewall to block external access to port 27017 unless you specifically need remote connections. On Ubuntu, use sudo ufw deny 27017 to block the port, then allow access only from trusted IP addresses if needed. Windows users should configure Windows Firewall to block inbound connections on port 27017. This prevents internet-wide scanning tools from discovering and potentially exploiting your MongoDB server.

Set up regular backups using mongodump to export your databases periodically. Create a backup script that runs mongodump –out /backup/mongodb/$(date +%Y%m%d) to generate dated backup folders. Schedule this script with cron (Linux) or Task Scheduler (Windows) to run daily or weekly depending on how frequently your data changes. Some VPS hosting providers offer automated backup tools that can include MongoDB data directories.

Install MongoDB Shell (mongosh) separately if it wasn’t included with your installation. Download it from MongoDB’s website for command-line database management. Consider installing MongoDB Compass, a free graphical tool for Windows, macOS and Linux that lets you visualise database structure, run queries and monitor performance without command-line work. Compass is particularly helpful when you’re learning MongoDB or debugging complex queries.

Review your configuration file to adjust settings like memory limits, log verbosity and network binding. The default configuration works for development but production servers often need tuning based on available resources and workload patterns. Finally, test that your web application can connect to MongoDB using the appropriate driver for your programming language (Node.js, PHP, Python or others). Verify connection strings work correctly and that your application can read and write data as expected.

Understanding how MongoDB fits into different hosting environments helps you choose the right setup for your project and avoid compatibility issues with hosting plans that don’t support custom database servers.

Most UK shared hosting providers like 123 Reg, Heart Internet and Krystal offer MySQL or MariaDB but not MongoDB. This limitation exists because MongoDB requires significant server resources (RAM and CPU) that shared hosting cannot allocate per customer without affecting other users on the same server. Shared hosting environments run on fixed resource pools where hundreds of accounts share the same server hardware.

MongoDB also needs root or administrator access to install and configure properly, which shared hosting doesn’t provide for security and stability reasons. Allowing custom database servers would let individual customers potentially crash or compromise the entire shared server. Most shared hosting uses cPanel or similar control panels that provide MySQL management but lack MongoDB integration.

If your project needs MongoDB, you must upgrade to VPS hosting or use a managed MongoDB service like MongoDB Atlas. Some managed WordPress hosting providers (WP Engine, Kinsta) might support MongoDB through custom enterprise setups, but this is rare and typically requires high-tier plans with dedicated resources. For typical web projects, shared hosting with MySQL remains the standard database solution.

VPS hosting gives you the server access and resources needed to install MongoDB yourself. Choose a UK VPS provider like Hostinger UK, Fasthosts, DigitalOcean or Linode and select a plan with at least 2 GB of RAM. Plans with 4 GB or more suit production environments where multiple applications share the server or you expect significant database traffic.

Select Ubuntu or Debian as your operating system during VPS setup. Most providers offer these as one-click installation options. Once your VPS is provisioned, connect via SSH using the credentials your hosting provider supplied. Follow the Linux installation steps covered earlier in this guide: add MongoDB’s repository, import the GPG key, install packages and configure the service.

Some VPS providers offer one-click MongoDB installation through marketplace apps or stack scripts. DigitalOcean’s Marketplace and Linode’s StackScripts provide pre-configured MongoDB images that automate the setup process. These installations handle repository configuration, package installation and basic security setup, saving you time if you’re less comfortable with Linux command-line work.

Remember that with VPS hosting, you’re responsible for server management including security updates, backups and performance monitoring unless you choose a managed VPS plan. Typical UK VPS hosting with sufficient specifications for MongoDB starts around £10 to £20 per month, though prices vary based on RAM, storage and bandwidth allocations.

MongoDB Atlas is the official managed cloud database service that handles installation, backups, scaling and security updates automatically. This removes the server management burden entirely, letting you focus on application development rather than database administration. Atlas offers a free tier with 512 MB storage that’s suitable for development and small projects, hosted on AWS, Google Cloud or Azure infrastructure.

Paid Atlas tiers start around $9 per month for production use with more storage, automated backups and performance monitoring. Pricing scales based on instance size, storage capacity and features like multi-region deployment. Compare this to self-managed VPS: Atlas costs more at scale but eliminates server management work, whilst VPS gives full control and potentially lower costs for large databases if you’re comfortable handling administration yourself.

Alternative managed options include AWS DocumentDB (MongoDB-compatible) and Azure Cosmos DB, which offer MongoDB wire protocol compatibility whilst running on their respective cloud platforms. These services suit organisations already invested in AWS or Azure ecosystems. For small projects and testing, Atlas’s free tier is excellent. VPS installation makes sense for cost-conscious developers comfortable with server management. Managed services suit businesses wanting hands-off database hosting without dedicating staff time to maintenance.

MongoDB Community Edition is free, open-source software that includes core database functionality, basic security features and community support through forums and documentation. This edition suits most users, from individual developers to small businesses running production applications. Community Edition uses the Server Side Public Licence (SSPL), which is free for most uses but has restrictions if you offer MongoDB as a service to customers.

MongoDB Enterprise Edition is the commercial offering with additional features that matter primarily to large organisations. Enterprise includes advanced security options like LDAP and Kerberos authentication, encryption at rest, monitoring tools (Ops Manager), commercial support from MongoDB Inc. and compliance certifications important for regulated industries like finance and healthcare. Enterprise requires a paid subscription with pricing that’s not publicly listed; you’ll need to contact MongoDB for a quote based on your deployment size and requirements.

The installation process is similar for both editions. Community Edition installs from public repositories as covered in this guide. Enterprise Edition requires a licence key during setup and uses MongoDB’s Enterprise repository. For development, small businesses and most web applications, Community Edition provides everything you need. Enterprise Edition becomes relevant when you’re running large-scale deployments, need guaranteed support response times or must meet specific compliance requirements that Community Edition doesn’t address.

Installing MongoDB successfully means following platform-specific procedures: the MSI installer for Windows, Homebrew for macOS or APT repositories for Linux Ubuntu and Debian servers. Each platform has its quirks, from Windows data directory creation to Linux GPG key imports, but the core process remains straightforward when you follow the steps systematically. Post-installation tasks like enabling authentication and configuring firewalls are essential, not optional, particularly for production servers exposed to the internet.

MongoDB suits modern web applications needing flexible data structures and horizontal scalability, but it’s not necessary for simple websites. Standard MySQL on shared hosting handles typical WordPress or basic CMS requirements perfectly well. MongoDB becomes relevant when you’re building custom applications with evolving data models, working with Node.js stacks or managing high write loads that benefit from document-based storage. The database requires VPS or dedicated server hosting with at least 2 GB RAM, as shared hosting environments don’t support custom database servers.

Managed services like MongoDB Atlas offer an alternative to self-hosting if you prefer hands-off database management. Atlas’s free tier works well for development and small projects, whilst paid tiers suit production deployments where you want automated backups, scaling and security updates without dedicating staff time to server administration. For UK website owners considering MongoDB, evaluate whether your project genuinely needs NoSQL capabilities, whether you have the technical skills or budget for VPS management and whether managed services might better suit your operational needs. If you’re unsure which hosting setup matches your database requirements, our free advice service can help you choose the right web hosting provider and configuration for your specific project.