WEB HOSTING FOR STUDENTS
Web hosting for students with a project to submit
Turn an HTML assignment, built class project, portfolio, resume, presentation or research document into one HTTPS link. Submit the browser result, then keep the same address if the work needs a correction.
Free plan, free SSL, no credit card.
- 1
- project site on the free plan
- 25
- publishes a day before the deadline
- 23
- framework guides for finding the output folder
- 0
- credit cards needed to start
How it works
Three steps, start to live link
-
Prepare the submitted version
Use one HTML file, a built site folder or ZIP, a PDF, a portfolio or the static output of your framework. Remove source files and secrets that the reader does not need.
-
Publish it at your project name
Drop the artifact, choose the address and wait for the live status. Open the link yourself on another device before putting it in the assignment.
-
Submit the link, not localhost
Paste the HTTPS address into the LMS, application or message. If you correct the project, re-publish behind the same address.
What students actually send
What students actually send
Web hosting for students puts browser-ready coursework and portfolio material on a public address. It is useful when an instructor, teammate or hiring manager needs to open the result without running the source project, installing packages or reaching a local development server.
The submitted artifact depends on the course. A first HTML assignment may be one file and can use single-file HTML hosting. A React or Vite class project needs its built output and the framework guide for the command and output folder. Raw HTML copied from a chat or class exercise can go through HTML to URL without creating a local file first.
Students also publish work that is not a website. A portfolio link can support applications, a resume link can stay current after edits, and a research PDF can open directly in a browser. The free plan keeps one site and does not require a card, but its pages are noindex, so it is suited to direct sharing rather than search discovery.
- HTML assignment A single page or small multi-file site submitted as the browser result rather than as source code alone.
- Framework project The static dist, build, out or other output folder produced after the project builds successfully.
- Portfolio Selected class, personal and collaborative work presented for internships, jobs or further study.
- Resume A PDF or HTML CV at a link that can stay fixed when the document is corrected.
- Presentation or research paper Slides, a poster, a PDF report or supporting media that should open without a drive-access request.
- AI-generated experiment HTML, JSX or a built project from an AI tool, checked and understood before it is submitted or shared.
Who it is for
The right publishing route for the assignment
Start from the format you have at the deadline. Do not rebuild a finished artifact only to make it fit another uploader.
-
Intro web students
Publish a first page with HTML hosting or paste it through HTML to URL.
-
Framework students
Find the build command and output directory in the framework guide hub.
-
Internship and job applicants
Collect work behind a portfolio link and keep the address current.
-
Graduating students
Give a current CV its own address with resume to link.
In detail
What you actually get
Submit the browser result at the level the course expects
A plain HTML assignment should not require a repository deployment, and a framework source tree should not be mistaken for a finished website. The upload path handles both by keeping the static boundary clear.
- A self-contained .html file can be uploaded on its own.
- A page with relative CSS, images or scripts should be uploaded with those folders intact.
- A framework project must be built first; the guides identify common output folders.
The assignment link survives a correction
A broken path or last-minute typo should not require a new submission address. Re-publish the corrected artifact to the same site and verify it before the deadline.
- The site address remains the same after each deployment.
- The free plan allows up to 25 publishes a day.
- Rollback begins on Pro if a later version is worse than the submitted one.
Learn the public-file boundary before it becomes an incident
A static build is public browser code. Secrets do not become safe because they are inside JavaScript, and copied project folders often contain files that were never meant for the web.
- Every deployment is checked for a .env file, .git folder and private-key material.
- API-key patterns in published JavaScript are flagged for review.
- If a real secret was exposed, remove it and rotate it; a warning cannot revoke it.
Keep a portfolio and resume outside the class folder
Coursework can become evidence of what you know when it is presented with context. Host the selected result, explain your contribution and keep personal application material separate from the assignment submission.
- Use portfolio to link for a selected collection of work.
- Use resume to link for a PDF or HTML CV that will change.
- Custom domains start on Pro when a professional address is worth adding.
A real example
Hand in work and share lessons as a link.
Educators & students
Submit a project, publish a reading, or share slides that open the same on every device.
- Assignment
- Project
- Slides
- Thesis
No card required
What the free plan includes
The free plan can host one active class project, portfolio or resume without a card.
- 1 live site on a real free plan, not a trial of a paid one, and no card to start.
- Up to 25 MB per upload and 25 MB of storage across the account.
- 5,000 visits and 5 GB of traffic a month.
- HTTPS with a real certificate, issued and renewed for you.
- Up to 25 publishes a day, so you can iterate without asking permission.
- The deploy-time security check, which reads what you published and warns about a stray .env file, a .git folder, a private key or an API key left in your JavaScript.
- A small Droply badge in the corner of the page. Removing it starts on Starter.
- Free sites are served noindex, so search engines do not list them. Search visibility starts on Starter.
- The same site address remains valid if you fix the project and publish it again.
A hosted project or Google Drive
Drive can deliver the files; hosting runs the result
Google Drive is the better handoff when an instructor needs the source ZIP, document comments or a folder of working files. A hosted link is better when the assignment is to open and use the finished website in a browser.
| Droply | Google Drive link | |
|---|---|---|
| What opens | The HTML, static site, PDF or portfolio is served as the published result. | A file or folder opens in the Drive viewer and can be downloaded according to permissions. |
| Running a website | HTML, CSS and browser JavaScript run at the site address. | Drive stores and previews files; it is not a static website origin. |
| Source-file review | Only the files you publish are presented. | A shared folder is better when the instructor needs source files and project structure. |
| Comments and collaboration | No document comments or shared editing. | Viewer, Commenter and Editor roles support review of the working file. |
| Correction | Re-publish at the same site address. | Manage versions, then Upload new version, can keep a non-Google file link. |
| Best fit | A browser-ready submission, public portfolio or current direct link. | Source files, folders, comments and collaborative documents. |
Google Drive rows checked 8 September 2026 against Google's file-sharing guide and its file-version guide. Sharing roles and product behavior can change. Confirm the required submission format with the instructor.
When Droply is the wrong choice
Use the submission system and format the course requires. A public hosted link is not automatically a valid assignment, and it is not a private course space just because nobody has shared the address widely.
- The instructor requires source code, a repository, a ZIP upload or a specific LMS submission. Follow that requirement and treat the hosted link as a supplement.
- The project needs a database, login, server action or private API key. Use an application host or change the project to a true static export.
- The work contains private class material, personal data or content you do not have permission to publish. Keep it in the approved school system.
- You need a database, a login system, or code that runs on the server. Droply serves files; it does not execute your application.
- You want a build to run on every push to a repository. Droply has no Git integration and no CI: you build locally and upload the result.
- You are running WordPress or another PHP application. A static export of it can be hosted here, but the application itself cannot.