Replit offers multiple ways to share projects publicly. You can publish a deployed app with a shareable URL, embed your Repl in external websites using an iframe, submit projects to Spotlight for community visibility, and customize your cover page with a description and tags. Public Repls are visible to anyone with the link, while the cover page serves as a landing page for your project.
Share Your Replit Projects with the World
This tutorial covers every way to share your Replit projects publicly, from simple URL sharing to embedding code in blog posts and submitting to the Replit Spotlight community. Whether you are building a portfolio, sharing a demo with a client, or showcasing a side project, Replit provides built-in tools to make your work accessible without any additional hosting setup. This guide is for beginners who have built something in Replit and want to show it off.
Prerequisites
- A Replit account (free Starter plan works for public sharing)
- A working Repl or deployed app you want to share
- Basic familiarity with the Replit workspace interface
Step-by-step guide
Publish your app to get a shareable URL
Publish your app to get a shareable URL
Click the Publish button (rocket icon) in the top-right corner of your Replit workspace. Choose a deployment type: Static for simple HTML/CSS/JS sites, or Autoscale for apps with a backend. After deployment completes, Replit assigns a URL in the format yourappname.replit.app. This URL is publicly accessible to anyone. Copy the URL and share it directly via email, social media, or messaging apps. If you are on the Starter plan, all deployments are public and expire after 30 days.
Expected result: Your app is live at a .replit.app URL that anyone can visit.
Customize your project cover page
Customize your project cover page
Every Repl has a cover page that acts as a landing page when someone visits your project's share URL. To customize it, open your Repl and click the project name at the top of the workspace. This opens the cover page editor where you can add a description of your project, select relevant tags for discoverability, upload a preview image or icon, and write instructions for users. A well-crafted cover page helps others understand what your project does before they open it.
Expected result: Your project cover page shows a custom description, tags, and preview image.
Share the workspace URL for code viewing
Share the workspace URL for code viewing
Beyond the deployed app URL, you can share a link to the workspace itself. Copy the URL from your browser address bar while the Repl is open. When someone visits this link, they see your cover page with options to view the code, run the app, or fork the project. Public Repls allow anyone to view the source code and run a copy. This is useful for sharing tutorials, code examples, or open-source projects where you want others to see and learn from your implementation.
Expected result: Visitors can view your code, run the app, and optionally fork the project from the shared workspace URL.
Embed your Repl in an external website
Embed your Repl in an external website
Replit provides an embed feature that lets you display your project inside an iframe on any website, blog, or documentation page. From your Repl workspace, click the share icon or use the embed URL format: https://replit.com/@YourUsername/YourReplName?embed=true. Add this as the src attribute of an iframe in your HTML. The embed shows a code editor and output panel, allowing visitors to interact with your code directly on your website. You can customize the embed by appending query parameters to control which pane is visible.
1<iframe2 src="https://replit.com/@YourUsername/YourReplName?embed=true"3 width="100%"4 height="500"5 style="border: none;"6 title="My Replit Project"7></iframe>Expected result: Your Repl appears as an interactive widget on your external website.
Submit your project to Replit Spotlight
Submit your project to Replit Spotlight
Spotlight is Replit's community showcase where developers share their best projects. To submit, make sure your cover page is complete with a clear description and tags. Then navigate to the Spotlight section in the Replit community area and submit your project. Well-received projects get featured and gain visibility across the Replit community. This is a great way to build a portfolio, get feedback, and connect with other builders. For teams building professional projects that need polished presentation, RapidDev can help ensure your deployment is production-ready before showcasing.
Expected result: Your project is submitted to Spotlight and visible to the Replit community.
Manage sharing permissions and visibility
Manage sharing permissions and visibility
Control who can see and interact with your project. On the Starter plan, all Repls are public. On Core and Pro plans, you can set projects to private, limiting visibility to yourself and invited collaborators. Collaborator permissions let you invite specific users to view or edit your code. When sharing publicly, remember that source code is visible to anyone. Never include API keys or sensitive data in code files. Use the Secrets panel for all sensitive values, as secret values are never visible to cover page visitors or project forkers.
Expected result: Your project visibility is set to your preferred level with appropriate collaborator access.
Complete working example
1<!DOCTYPE html>2<html lang="en">3<head>4 <meta charset="UTF-8">5 <meta name="viewport" content="width=device-width, initial-scale=1.0">6 <title>My Replit Project Showcase</title>7 <style>8 body {9 font-family: system-ui, sans-serif;10 max-width: 900px;11 margin: 40px auto;12 padding: 0 20px;13 }14 h1 { color: #0D0D0D; }15 .embed-container {16 border-radius: 12px;17 overflow: hidden;18 box-shadow: 0 4px 12px rgba(0, 0, 0, 0.1);19 margin: 24px 0;20 }21 .embed-container iframe {22 border: none;23 width: 100%;24 height: 500px;25 }26 .links {27 display: flex;28 gap: 16px;29 margin-top: 16px;30 }31 .links a {32 color: #F26207;33 text-decoration: none;34 font-weight: 600;35 }36 .links a:hover { text-decoration: underline; }37 </style>38</head>39<body>40 <h1>Project Demo</h1>41 <p>Explore the code and run it directly below.</p>4243 <div class="embed-container">44 <iframe45 src="https://replit.com/@YourUsername/YourReplName?embed=true"46 title="Interactive Replit Project"47 loading="lazy"48 ></iframe>49 </div>5051 <div class="links">52 <a href="https://yourappname.replit.app" target="_blank">Live App</a>53 <a href="https://replit.com/@YourUsername/YourReplName" target="_blank">View Source</a>54 </div>55</body>56</html>Common mistakes when sharing Replit projects publicly
Why it's a problem: Sharing a project with API keys hardcoded in the source code
How to avoid: Move all sensitive values to the Secrets panel (Tools > Secrets). Source code is visible to anyone who views a public Repl.
Why it's a problem: Sharing the workspace URL expecting it to show the running app
How to avoid: The workspace URL shows the cover page and code editor. To share the live app, use the deployment URL (yourappname.replit.app) instead.
Why it's a problem: Assuming Starter plan deployments are permanent
How to avoid: Free Starter plan deployments expire after 30 days. Upgrade to Core or Pro for persistent deployments, or redeploy periodically.
Best practices
- Always complete your cover page with a clear description, tags, and preview image before sharing publicly
- Use the Secrets panel for all API keys and sensitive data since cover page visitors and forkers cannot see secret values
- Test your deployed app at the .replit.app URL before sharing to ensure everything works outside the workspace
- Add ?lite=true to embed URLs for a cleaner, minimal embed on external websites
- Include clear usage instructions on your cover page so visitors know how to interact with your project
- Check that your project runs correctly when forked, since forked copies do not inherit secret values
Still stuck?
Copy one of these prompts to get a personalized, step-by-step explanation.
I built a [type of project] in Replit and want to share it publicly. What are all the ways I can share it? I want to embed it on my personal website, submit it to the Replit community, and share a direct link. Walk me through each option.
Help me set up my project for public sharing. Add a clear description to the cover page, make sure no secrets are exposed in the code, and generate an embed code I can paste into my website. Also check that the app works at the deployed URL.
Frequently asked questions
Yes. Public Repls expose your source code to anyone who visits the workspace URL. Use the Secrets panel for API keys and sensitive data since those values are never visible to visitors or forkers.
No. When someone forks your Repl, they see the secret names but not the values. They must add their own secret values to make the forked project work.
No. The Starter plan only supports public Repls and public deployments. You need a Core ($25/month) or Pro ($100/month) plan for private projects.
Add ?embed=true&output=1 to the embed URL. This loads the output panel by default and runs the Repl automatically when a visitor opens the page.
Starter plan deployments expire after 30 days. You can redeploy to extend the period, but for permanent hosting you need a paid plan.
Yes. RapidDev can assist with preparing production-ready deployments, optimizing performance, and creating professional project presentations. They help ensure your shared project makes the best impression.
Spotlight is Replit's community showcase for outstanding projects. Submit your project after completing the cover page with a description, tags, and working demo. Projects with clean code, good documentation, and creative implementations are most likely to be featured.
You can hide files from the file tree using the hidden key in your .replit configuration file, but this only hides files in the GUI. Determined users can still access hidden files through the Shell. For truly sensitive files, use Secrets instead.
Talk to an Expert
Our team has built 600+ apps. Get personalized help with your project.
Book a free consultation