dhosty

Hosting & servers · 7 min read

Free web hosting: how to plan your first website

Free web hosting is a good way to get started if you want to publish a small static website and the limits of the offer match your project. dhosty's free entry includes 50 MB, its own dhosty address and the website builder. It includes HTML, CSS and images. For PHP, databases and SFTP you need suitable paid packages. Therefore, before uploading files, it is worth taking a short inventory: What should the site be able to do, which content is already available and how do you want to maintain it later?

A static website starts with a clear purpose

First, determine what task your website should do. For a personal idea, a small project description or a manageable information page, prepared content is often sufficient. Visitors will retrieve files that you have created and published before. You do not need an application with user accounts or a database to do so automatically. First, write the most important information together in a simple document and decide which pages to create.

This preparation helps you to realistically classify the offer. A static website is not an extensible platform for any application. If visitors are to store, log in or retrieve individual data themselves, additional requirements are added. Check such functions individually. The free entry should fit your actual project. It does not replace the check whether a specific software can be operated with the tools and technical limits provided at all.

What is included in the free dhosty entry

The area free web hosting describes how to get started with 50 MB of web space, its own dhosty address, and the website builder. For planning, it is not only the memory number that counts. It is equally important that this environment is intended for static HTML, CSS and image files. You can publish content that the browser can display directly. Check the current product description before transferring files to an existing application or requiring additional services.

Do not derive functions from a general hosting name that are not included in the free package. PHP, databases and SFTP belong to suitable paid offers. Also a tool shown on another side does not have to be automatically part of the free entry. If you are unsure, write down the specific function and match it with the product page. This saves you a setup that later fails due to a basic technical requirement.

Put together HTML, CSS and images meaningfully

A small website usually consists of several related files. HTML describes the content and its structure, CSS specifies the presentation and images complement the information. Make sure that references to images and stylesheets match the actual folder structure. A locally functioning file path can lead to the void after publishing if it points to a folder of your own computer. Use comprehensible file names and control associations after each change.

Keep the first version consciously manageable. A clear start, understandable headlines and easy-to-read paragraphs are more helpful than many incomplete subpages. Check the display even with a narrow window and on a smartphone. Texts, navigation and images should be usable without lateral moving. If you use the build kit, check the published result nevertheless. An editing preview does not automatically answer whether all links and content can be reached correctly under the public address.

Dealing with 50 MB consciously

The existing memory contains the files of your website. Images often require much more space than HTML and CSS. Therefore, consider what resolution makes sense for the actual presentation. A photo that appears only as a small preview image does not need to be published in the original camera resolution. Create suitable web files and keep your originals separately. The publication does not replace your own storage of your source data and editable designs.

After major changes, check the scope of your project. Remove outdated files only if you are sure that no published pages will point to it. Don't accidentally drop backup copies in short web space if you can also keep them outside the website. A small, tidy file structure facilitates later updates. However, no fixed number of visitors or guaranteed speed can be derived from the memory size alone. Further properties of the website and their use play a role.

When an application needs more than static files

Many website templates contain functions that at first glance seem ready. A form can be visible, for example, without the processing of its entries being set up. Therefore, check what actually happens after sending and which service would be responsible for it. A static file does not perform any server-side PHP processing. Likewise, a database project stored on your own computer is not automatically available on your public website.

If your software requires PHP or a database, compare the appropriate [web hosting packages].](/webhosting/) using their current functions and quotas. Write down additional versions and extensions required from the software documentation. A package change is then a decision based on specific requirements. It is not enough to select only more memory if the decisive runtime environment is still missing. If you ask, describe as precisely as possible which application you want to use and which requirement you cannot assign on the product page.

Check the address, publication and maintenance separately

The dhosty address is a way to access your published website. A separate domain is another planning step and not the same as the storage space for your files. If you already have a name, check the possibilities to connect the domain and the necessary settings. Do not change existing DNS entries indiscriminately. In particular, website and mail settings concern different services that you should document separately before switching.

The Guide to Connecting a Domain Helps you to sort out the next steps. First, test your website at the available address before changing any other references to it. Check the home page, subpages, images and navigation. Then plan the ongoing maintenance: Who updates information, where are the original files and how do you document changes? A free release will only be practical if you can find your content later and edit it reliably.

Keep the first start small and justify extensions

You don't need a comprehensive function catalog for the first release. Start with the most important content, control the result and collect concrete improvement requests. A missing image or incomprehensible navigation can often be fixed by a targeted change. Another application case may require additional hosting functions. Separate these questions so that a complete reconstruction does not arise from a small correction.

When your project grows, you can see what has changed: more files, a dynamic application, a database or other access paths. Compare a suitable offer only afterwards. A Linux operation is not automatically required for a normal small website; the guide [VPS or Webhosting].](/ratgeber/vps-oder-webhosting/) This way, you can use free web hosting as a manageable introduction and plan later extensions based on verifiable requirements instead of fixing them to product names or general performance promises alone.

Frequently asked questions

Can I use PHP in the free dhosty package?

The free entry is intended for static content such as HTML, CSS and images. For PHP you should check a suitable paid web hosting package. Compare also the requirements of your application so that additional required functions and quotas are actually included.

What role do images play in 50 MB webspace?

Images can take up a large part of the available memory. Therefore, publish a resolution suitable for display and keep original files separately. Also, check whether old files are still needed before removing them from your project.

Is your domain the same as web hosting?

No. The domain is the name where a service can be reached. Web hosting provides the environment for your website files. Connecting an existing domain requires appropriate settings and should be checked separately from existing mail settings.

When should I compare a paid package?

If specific requirements go beyond the free entry: for example PHP, databases, SFTP or other quotas. Note the actual need and compare it with the current offer. More memory alone does not replace any missing technical function of your application.

More hosting topics