Webnode explained: projects, languages, backups and exit limits

Who Webnode fits

Good for: an owner with a defined set of pages, ordinary navigation, contact enquiries and a willingness to work within a hosted editor. It is particularly worth considering when avoiding server administration matters more than having direct control over the application and its files.

Less suitable for: a project whose essential requirements include a custom application, unrestricted design code, or moving the finished website to another host without rebuilding it. Those are architectural requirements; a higher subscription does not automatically solve them.

Consider a Portuguese consultant publishing services in Portuguese and English. The useful comparison is the plan that covers two languages, a custom domain, the required form and a recovery method. Comparing the cheapest headline plan with a complete WordPress setup would overlook different jobs. For three separate consultant sites, calculate three project subscriptions rather than assuming one upgraded account covers all of them.

Premium belongs to one project

Webnode states that Premium extends features and storage, is required for a custom domain and applies to one website, rather than every project in the account. This is a material distinction when you run several brands. Keep the invoice, domain and project name together when recording renewal dates. See the official explanation of what Premium includes and how it is assigned.

You can connect a domain held with another registrar; transferring its registration to Webnode is a separate choice. Email is separate again: the domain connection instructions require Webnode mail records only if you intend to use Webnode email. Keeping an existing mail service can therefore be part of the setup. Webnode also explains that externally managed DNS problems may require help from the registrar. These distinctions are documented in its domain assignment guide.

Our Webnode domain and email guide covers the connection checks. Before paying for duplicate mail services, decide who will host the website, who controls the domain and who delivers your email.

Check editor limits before building everything

Webnode’s editor FAQ says direct CSS editing is unsupported and the selected template cannot simply be switched for another. It also states that source files are unavailable and the completed website cannot be transferred to another hosting provider. Third-party HTML embeds may work, but universal compatibility is not promised. See the editor and content FAQ.

Webnode maintains a separate help section for the previous editor. Match instructions to the project you actually have; an old screenshot is not evidence that a control or entitlement exists in the current editor. This guide uses the current support articles linked here.

Build your hardest representative page first: a long service page, a substantial gallery or the required enquiry form. Check it on a narrow screen. A short trial of the essential layout is more useful than recreating forty easy pages before discovering a missing requirement.

Hosted infrastructure still needs an owner

Webnode hosts the site on its own servers. That reduces the infrastructure you administer; you still need someone responsible for account access, domain renewal, content changes and enquiries. Record which collaborator can edit which project and keep the account recovery route accessible.

The administration documentation identifies Premium website security as an optional add-on, with form protection, IP filtering and antivirus scanning. It also lists optional integrations for privacy tools, booking and invoicing. Do not assume every feature shown in the administration screen belongs to the website subscription. See Webnode’s administration overview.

Adding an integration creates another dependency to check: who receives the data, what the visitor sees and what happens if the service expires. A platform feature does not establish that your particular form, consent wording or retention practice is appropriate.

Recovery and portability solve different problems

Make a manual recovery point before a major change and check the space it will consume. The manual backup scope and limits apply to the active project. Automatic backups have separate documentation and terms: establish whether that service is active rather than treating a manual allowance as an automatic schedule.

Restoration affects the entire project, including shop orders, stock and form data. It cannot recover just one page. Orders newer than the selected snapshot are deleted by that rollback, according to the official restore instructions.

For example, restoring Monday’s snapshot after a Wednesday design mistake can also remove orders received on Tuesday. First establish whether correcting the page manually solves the problem. If a full restore is necessary, preserve recent records and decide how to reconcile them; do not promise that downloading a list automatically recreates the missing transactions.

These recovery snapshots do not constitute a portable website package for another host. Webnode separately documents CSV export of form submissions and product export. Those can help retain particular data, but do not export the complete design, navigation and application. Keep original text and image files outside the builder, and read our builder exit checklist before cancelling.

Make the decision around the difficult requirement

Choose Webnode when the essential page, language, form and recovery requirements fit and you accept a future move may require rebuilding. Pause when the necessary feature depends on unsupported code, an unverified embed or a portability assumption.

Compare another hosted builder if its documented workflow fits better. Compare self-hosted WordPress when application control and host portability justify arranging maintenance and recovery yourself. Our website builder versus WordPress guide explains that operating tradeoff.

Before buying, verify the representative page on mobile, the correct project and plan, the full invoice, domain and mail ownership, and the impact of a full-project restore. Those checks connect the purchase to how the site will actually be run.