Render Discord Bot Hosting: Free Limits and Setup

Choose a worker or a web service

Render background workers run continuous processes without a public HTTP listener. That suits a Gateway bot. This is a deployment recommendation based on its architecture, rather than a requirement to add a queue to your bot.

A web service suits an application with an actual HTTP endpoint. Discord supports receiving interactions over HTTP, which differs from a persistent Gateway connection. That endpoint must verify Discord requests. Render web services must listen on 0.0.0.0 and the configured port; see port binding.

Adding an empty Express server just to satisfy a web platform does not make a sleeping service dependable for Gateway events.

What Render's Free plan means for bots

Render's Free instance documentation lists web services, Postgres and Key Value; it does not include background workers. Free web services spin down after 15 minutes without inbound traffic. An outbound Discord Gateway connection is not a replacement for inbound traffic to your web service.

Use the current Render pricing page to check worker compute, storage and other charges before creating a service. A workspace plan and a service's compute plan are separate choices. For a quiet Gateway bot, choose suitable continuous compute rather than relying on a ping service.

Prepare a Node.js or Python project

Make sure the project starts locally before moving it. For Node.js, commit package.json and a matching lockfile, with runtime packages such as discord.js under dependencies. For Python, commit requirements.txt with the packages your bot imports. Keep .env, tokens and installed dependency folders out of Git.

Use these command patterns, adjusting filenames to match your project:

TypeScript needs its build tools and a compile step before starting the generated JavaScript. Do not omit development dependencies during that build if the compiler is declared there.

Connect your repository and branch to the chosen Render service. Set BOT_TOKEN privately in environment settings, matching the variable your code actually reads. Check the deployment logs for successful login, then test a command in a test server. For a copyable starting point, see our minimal discord.js bot or discord.py example.

Protect saved data before redeploying

Render's default filesystem is ephemeral. Its persistent disk documentation explains which paid services can attach a disk and which paths survive restarts and redeploys. If your bot stores SQLite files, uploads or other state, configure appropriate persistence or an external database before relying on it. Source in Git is not a backup of live data.

Move from Render to DiscordBotHost

1. Copy your source, dependency manifests, entry filename and environment-variable names. Export persistent data separately while writes are stopped.
2. Compare Free limits with your bot's memory and disk use. Free has 256 MB RAM, 1 GB disk and renewal every 7 days. Starter is $0.99/month with 512 MB RAM and no weekly renewal.
3. Choose the matching runtime, set the token privately, and upload the project or connect GitHub. Free supports public repositories; private repository credentials require a paid plan.
4. Stop the old process before starting the replacement. Test commands, permissions, scheduled work and saved data, then watch the console for errors.

Keep Render if its wider application stack fits your project better. A bot with an HTTP dashboard, queues or managed data services has different requirements from one small command bot. Our Railway, Render, Replit and Heroku comparison covers the broader choice. For a bot that is already online but silent, start with troubleshooting.

Sources and scope

Render and Discord documentation linked above was checked on Oct 31, 2026. Plan availability can change. This guide is published by DiscordBotHost, a hosting provider; compare the workflow and limits against your own requirements.

Questions

Sources

1. 1https://render.com/docs/background-workers
2. 2https://docs.discord.com/developers/interactions/receiving-and-responding
3. 3https://render.com/docs/web-services#port-binding
4. 4https://render.com/docs/free
5. 5https://render.com/pricing
6. 6https://render.com/docs/disks
7. 7https://discordbothost.com/pricing/