Free
1 Website
no licence needed
ZIP export, note in the footer
Download PagesProducts
Community
DiscordAsk questions and read the news firstThemes for WebDonkeyColour schemes for the app, from the communityThemes for the EditorColours, font and cursor, from the communityIssuesSee known issues and report your own. A helpful report can earn you a bonus.
WebDonkey Pages
You describe in the chat what you need. Pages writes the website, checks it after every change and puts it on your server, all on your Mac and without a line of code.
Free covers one website with every feature plus the ZIP export. More websites and publishing straight to your server come with a Pages plan.
New: WebDonkey Pages
You describe in a chat what the website should show. Pages builds it with its own design, checks it and publishes it to your server. It runs on your Mac, with or without WebDonkey.
Personal for personal accounts, Business, Studio and Agency for business accounts. Add 5 websites at a time to the business plans.
Free
1 Website
no licence needed
ZIP export, note in the footer
Download PagesPersonal
3 Websites
00,00
for personal accounts
Buy in the shopBusiness
3 Websites
00,00
for business accounts
Buy in the shopStudio
10 Websites
00,00
for business accounts
Buy in the shopAgency
30 Websites
00,00
for business accounts
Buy in the shop+5 websites for Business, Studio or Agency: 00,00
Final prices including the VAT of your EU country (in Monaco the French VAT), outside the EU and Monaco without VAT. No shipping costs. Business prices apply to company accounts; what the plans include is set out in the service description.
Install Pages, create your first website and see what works without a licence. Plus the overview of all your websites: create, import, take over, back up and archive.
Pages runs on your Mac and builds websites through conversation. You never see code, a terminal or build errors, and the preview shows the latest version that passed every check. You don't need WebDonkey for any of it.
Open the DMG, drag WebDonkey Pages into Applications and launch it. If anything is missing, the overview lists it in the notice "Pages is not ready yet:". The Pages kit, which Pages builds and checks with, is part of the app and is renewed with every update.
Node.js 22.12 or newer, Google Chrome, Chromium or Microsoft Edge for the checks, and an AI access: your signed-in Claude Code or an Anthropic API key. Settings › Technology lists each tool with its location or as "missing".
New website, enter a name, Create. The chat asks what you offer, for whom and where, and Pages builds a first draft from it. Pages asks for missing details or collects them under Facts; nothing is made up.
Pages runs fully on its own, with a licence too. If WebDonkey is on the same Mac, Pages connects by itself and adds the local test with PHP, the same language, your themes from WebDonkey, with Premium the servers you saved there, and the option to use its licence key. Pages always checks its licence with the shop itself. The badge at the top right shows whether Pages runs with or without WebDonkey; if WebDonkey is too old, Pages runs on its own until WebDonkey is updated.
Without a licence you build one website with everything Pages can do and export it as a ZIP with the link "Built with WebDonkey Pages" in the footer. A Pages package adds more websites, publishing straight to your server, the footer without the link and submitting your own themes to the gallery. The AI always runs through your own access.
The overview is the start view of Pages: every website as a card with name, status and date, and above them your package and how many websites are in use. Active websites count, drafts included.
Enter a name of up to 80 characters and choose the AI access: as in Settings, always Claude Code, or the Claude API with a key of its own, such as your client's. The name becomes the folder. Free has one website, a Pages package as many as your allowance covers.
You can change name and AI access at any time, even for an archived or locked website. The folder stays the same when you rename. A website's own API key stays encrypted in Pages on this Mac and is only sent to Anthropic.
Brings back a website you backed up with Pages, as a folder or a ZIP file. Pages takes over data, design, photos, chat and history, plus server, port, user and web folder for publishing, creates the website anew and builds it with the current version, no AI needed. You choose the AI access as when creating a website, and if the name is taken, Pages suggests a free one. A backup never contains a password, and the allowance applies as when creating a website.
If you choose the folder of a website built with the Page Builder toolkit under Import website, Pages takes over its photos, fonts and favicons and has the AI rebuild it step by step, with the copy taken from the original, in 30 to 90 minutes depending on size. The AI only starts once you click Start takeover in the workspace, and you can stop and continue later at any time. Pages lists what is not taken over. The original stays untouched.
Export backup in the Publish website window puts the whole website with data, design, all photos, chat and history as a ZIP into your Downloads folder, plus server, port, user and web folder for publishing. It always works, in Free too and for an archived or locked website. Passwords and API keys are not included.
Every card carries a badge: Draft, Published, Open facts, Update pending, Locked or Folder missing. Open facts means something is listed under Still missing, or the domain or host is missing. Update pending means the published website has changed since or a newer kit is installed: publish it again. A website is locked when your package has no place for it; the oldest ones stay active. Viewing and exporting still work, and editing does again once a place is free.
Archiving saves the website as a ZIP in its folder and frees its place in your allowance. Viewing and exporting still work, and you reactivate it once a place is free.
The workspace of a website: the preview at full width, the chat with the AI on the left, the menu with pages, facts, checks and history on the right. After every change Pages checks the website by itself.
When you open a website, the preview takes up the full width. The chat sits on the left, the menu with pages, facts, checks and history on the right, and both slide open when you move the pointer to their handle at the edge. The workspace is fully included in Free.
Shows the website the way visitors will see it, with the latest version that passed every check, and until there is one, with the first successful build. If a check is red, the last green version stays on screen, on reload too, and export and publishing take exactly that one. Links work as on the real website, and Open in browser shows the same page in your browser.
Both are panels on top of the preview. Hovering slides them open, a click on the handle opens or closes them, Escape closes them. The pin keeps a panel open, separately for chat and menu and after a restart too. The Facts tab shows the number of open questions, the Checks tab the number of red parts.
At the top right: Show folder in Finder, Edit website, Undo, Test in WebDonkey and Publish. Next to them you see what Pages is doing, such as building, checking or publishing. Pages only ever works on one thing per website.
Restores the most recent saved state, rebuilds the website and checks it before it appears in the preview. Each further click goes back one more state. Deleted photos the earlier state needs come back. There is no redo; ask the AI again instead.
Opens the Publish website window. It first shows what is still missing, then the ways out: straight to your server with a Pages package, or as a ZIP, in Free too. The same window exports the backup.
In the chat you describe in your own words what you offer, for whom and where. The AI turns that into pages, copy and a design of its own, has the result checked and tells you briefly what it changed and what it still needs to know.
Enter sends, Shift+Enter starts a new line. To get you started there are three example messages, and a click puts one into the field. Give concrete facts and say how the site should feel; Pages works through larger requests in one run. Pages stores the chat per website.
Every message is a run in fixed steps: save the state, the AI works only with Pages' own tools, then build and check. If something is red, the AI fixes it for at most two rounds, otherwise the previous state is back. You follow the progress live, and Stop cancels.
Pages builds with Claude, through your signed-in Claude Code or an Anthropic API key. You set it once in Settings and, where needed, per website, for example with your client's key. The status bar shows which access applies right now.
Answers appear as formatted text with lists, tables and code; you can select and copy text, and Copy code copies a code block. Links open in your browser, images from the web are not loaded on their own, and HTML stays text. If Pages discarded a change, the note appears below the answer.
The Pages tab shows every page with its address and, below it, its sections in the order they appear on the page. You change the structure in the chat, and a click on a page shows it in the preview.
Every page is a card with its name in the website's menu and its address. You add, rename or take pages out of the menu in the chat. Pages checks the title and description for search engines too, and that no link leads nowhere. From your facts Pages also builds structured data following Schema.org and an llms.txt for AI search systems, plus robots.txt, a 404 page of its own and, once the domain is entered, a sitemap.
A coloured dot marks a section designed just for your website, such as a small calculator or an interactive overview; a grey dot marks a tested template from the kit, from the big entrance through services and process steps to the contact form. The AI only uses key figures, prices and testimonials with facts you have confirmed.
Both pages are created from your facts, and the links sit in the footer of every page. While details are missing they show visible placeholders, and Pages only publishes once everything is complete. They are templates: read them, have them checked if needed, then confirm them.
The Facts tab collects the details your website needs: domain, host, the business's name and address, contact details and register entry. Whatever the AI learns in the chat it enters itself, and you can edit every field yourself too.
Whatever the AI needs but doesn't know becomes a question under Still missing, and it asks you in the chat. Once the detail is there, the question disappears. The preview keeps working; publishing only works once nothing is open.
Pages needs the domain for the fixed addresses of the pages and as the target when publishing. The host's name and address belong in the privacy policy, and Use profihost GmbH fills both fields with that provider's details.
Name, legal form, representation, address, phone, email, VAT ID and register entry. Pages checks that the required details are complete, such as who represents the business, a second fast way to get in touch besides email and, for a GmbH, UG or e. V., the register court and number.
Once you have read the legal notice and privacy policy and the details are correct, tick the box. Without this confirmation Pages won't publish. If you change business details later, read both pages again.
Drag photos from Finder into the window and tell the AI in the chat where they should go. All photos of a website are listed in the Pages tab. Without photos Pages designs the website with type, colour and shapes and asks you for some.
Drag one or more photos into the window and let go. Pages copies them into the website's folder and gives them simple lower-case file names; the original in Finder stays unchanged.
The AI only knows the photos by their file names. Give the name and briefly describe what the photo shows; that also becomes the alternative text for screen readers. Tiles labelled in use are used on the website.
A photo that isn't used anywhere goes with one click. If it is in use, Mention in chat puts a suggestion into the input field, and afterwards you can delete it. Pages keeps the last 40 deleted photos, and an earlier state brings them back.
Pages checks the website by itself: build, content and links, external sources, the details required for the legal notice and privacy policy, accessibility and the layout on narrow screens. Before publishing, the full check with Lighthouse is added.
Runs after every change from the chat and with Check now. It rebuilds the website and checks content, links, external sources, open facts and required details, plus accessibility and width in a browser. For that Pages uses Google Chrome, Chromium or Microsoft Edge.
At the top the summary with date and time, green when the website is ready to publish. Below it each check part with a tick, a yellow warning triangle or a red sign and the number of findings. Red you have the AI fix in the chat; yellow usually means adding facts.
Page titles up to 60 characters, descriptions of 120 to 160, exactly one main heading, alternative text on every image. Nothing from external servers, no iframes, no links that lead nowhere, and a legal notice and privacy link on every page. Accessibility is checked with axe at 390 and 1440 pixels wide.
Additionally measures every page meant for search engines with Lighthouse on mobile, in one to two minutes. It runs by itself before every publish to your server, or when you click. If performance falls below the threshold, Pages measures the page once more and the better score counts.
Before every change Pages saves the state of your website. The History tab lists these states, newest first, and takes you back to an earlier one in two clicks.
Content, pages and design are saved before every chat message. If the AI changed nothing, Pages removes the saved state again. Deleted photos are kept separately, and what you enter yourself under Facts goes into the history with the next saved state.
Back to the state before this change, confirm, done: Pages restores that state and rebuilds the website, the facts included. The chosen entry and all newer ones leave the history, and the chat stays as it is.
Only a version that passed the full check goes online. Straight to your server via SFTP, as a ZIP for any host, or tested locally in WebDonkey first, with PHP for the contact form.
The Publish website window brings the ways out together: straight to your server via SFTP, as a ZIP for any host and as a backup of the whole website. Only a version that passed the full check goes online, Lighthouse included.
At the top you see what is still missing: open facts, the domain, the host for the privacy policy and your confirmation of the legal pages. Before uploading, Pages checks the website completely. If anything is still open or red, Pages uploads nothing and gives the reason.
Enter server, port, user, password or SSH key and web folder, then Check and publish. Each file arrives under a temporary name and only then replaces the old one, and afterwards Pages checks under your domain whether the new site shows up. If the web folder already holds other files, Pages moves them into a hidden backup folder when you agree. For a contact form Pages creates the sending settings. From the Personal package on.
The finished website with instructions in your Downloads folder, for any host and for archived or locked websites too. In Free the footer carries the link "Built with WebDonkey Pages", a plain text link without any script; from the Personal package on it is left out.
To publish straight to a server, Pages needs SFTP access to your web space or server, remembered per website. With a host, access and web folder are enough; a fresh server of your own without a web server Pages sets up itself.
The server without https:// and without a path, the port (usually 22), the user, sign-in by password or SSH key, and the web folder your host set up for the domain. With WebDonkey Premium you pick a server saved there and Pages fills in the access. Password and passphrase stay encrypted on this Mac, only apply to the server you saved them for and never go into the website's folder or a backup.
Shows whether sign-in works, whether the web folder exists and Pages may write there, and whether a web server is already running. If anything is missing, Pages offers to prepare the server.
On the first connection Pages remembers the server's fingerprint and compares it every time after. If the server identifies itself differently than last time, Pages shows a red warning. Until the fingerprint is confirmed, Pages uploads nothing.
On Debian and Ubuntu with shell access: Caddy from the official package source, the web folder, secure settings, HTTPS through Let's Encrypt and ports 80 and 443. The plan is shown in plain words first, and nothing starts before you click. Pages doesn't store the sudo password. Mail sending for the contact form is not part of this setup, and Pages tells you so.
When testing, publishing and preparing, Pages names the reason in plain words and says what you can do: wrong port, key not accepted, web folder missing, no SFTP for this account or no space left on the server.
If WebDonkey is installed and running, you test a website at a local address with PHP and can try the contact form too, before it goes online. Without WebDonkey only this test is missing. You don't need a Pages licence for it.
Test in WebDonkey, Set up now: if there is no build yet, Pages builds first, then WebDonkey sets the website up. The address then appears on the button, with a green dot while it runs. It gets HTTPS as long as WebDonkey has room for one more site with SSL.
In WebDonkey the website runs with PHP, and the form checks your input as it would online and really sends, but to Mailpit: the message appears in WebDonkey under Mail, never in a real inbox. Pages starts Mailpit for it, and tells you if it still isn't running. Publishing and export never take these test settings along.
The button with the local address takes it out of WebDonkey again. Your website stays as it is, and you can set the address up anew at any time.
On WebDonkey's Sites page, built Pages websites not set up there yet are listed under From WebDonkey Pages, and Set up locally sets them up; the ones already set up carry the Pages badge. Open in Pages brings Pages to the front and opens the website. WebDonkey only reads the folder of your Pages websites.
AI access and technology, docs and features right inside Pages, the colours of the app, your licence with package and allowance, updates when you click and the open-source licences.
The gear at the top right opens Settings, from top to bottom: AI access, licence, appearance, updates, technology, and legal and open source.
Two cards: My Claude Code uses your signed-in Claude Code on this Mac, which Pages only gives its own tools. Anthropic API key uses a key from the Anthropic console, and the costs are billed to your Anthropic account. Check and save tests the key and stores it encrypted.
Shows what Pages works with on this Mac: the Pages kit, Node.js 22.12 or newer, the browser for checks, Claude Code and the websites folder. If something is missing, the row says so and a line below tells you what is needed.
Without WebDonkey, Pages follows the language of your Mac; with WebDonkey it follows WebDonkey's, as long as that is German or English. The checks and the work steps in the chat follow this language. The language of your website doesn't depend on this.
Themes set the colours of Pages itself, not those of your website. A theme of your own is four decisions: light or dark, a background and two accents. Pages derives every other colour from these, like WebDonkey.
A click applies the theme right away. Built in are Aurora (dark), Arctic (light) and System, plus Follow WebDonkey when WebDonkey is there. Add ready-made presets, your own themes and, with WebDonkey, copies of your themes from there.
Name, a dark or light base, background, accent and second accent, plus an icon. A large preview shows text, muted text, status colours and buttons in these colours. Any built-in theme or preset can be edited as a copy.
Themes other people shared, sorted by new or popular, with a fuzzy search. Pages only loads the list from webdonkey.io when you click. Take over puts a copy under Your themes.
Share your own themes with others. They appear once they have been checked and approved, and your name is never shown. At most three submissions wait at the same time, and you can withdraw a waiting one at any time.
Without a licence Pages is fully usable for one website. With a Pages package you create more websites and publish straight to your server. Pages checks its licence with the shop itself, independently of WebDonkey, and syncs it every 10 minutes.
Paste the key, Activate: the badge then shows your package, such as WebDonkey Pages Business, with device and term. If WebDonkey has a key, Pages offers to use it. If a key contains no Pages package, Pages runs as Free.
Every package unlocks publishing straight to your server and brings an allowance of active websites, and add-ons extend it. The Licence area and the overview of your websites show the usage. A package you bought but haven't assigned yet you assign in your shop account.
Offline the licence stays active, and Pages says until when. A licence is valid on one device at a time, and WebDonkey and Pages on the same Mac share the seat; if it is active on another Mac, the seat moves over by itself after about 15 minutes of silence. After an expired subscription, the next payment unlocks the package again.
Pages looks for new versions by itself, shortly after launch and then every 10 minutes. It only installs when you click, because the restart stops the preview and running jobs. Your websites stay as they are.
When Pages finds a new version, it shows it with its release notes once per version, as soon as you are not typing and no other window is open. The status bar shows a pending update, and Settings › Updates › Check now asks right away.
Install now asks the shop once more, downloads the update, checks its signature and restarts Pages, with the progress in per cent on the button. Let running work such as a takeover or a publish finish first.
Every version with its changes, the installed one marked, older ones loaded on request. It opens with What's new in Settings or in the update notice. Pages doesn't load images in release notes on its own.
You can also read the docs and this overview of every feature right inside Pages: click the book icon next to the gear at the top right of the title bar. Pages loads both from the shop, so you always read the current version.
The topic tree with sections, chapters and the individual features sits on the left, the text on the right. The search filters by titles and text. A link to another chapter opens it straight away, links into the WebDonkey or editor docs open in the browser. Pages has no built-in copy of the docs as a fallback.
This features page inside Pages: the contents with sections and chapters on the left, and for each chapter a picture, its sub-points and a badge showing what Free includes and what needs a package. "Read in the docs" opens the matching chapter in the guide, and a click on a picture enlarges it.
Legal and open source lists every open-source component in Pages with its licence and the full licence text. Plus when Pages goes online and what stays on your Mac.
Every component from the app, the Rust libraries and the Pages kit, searchable by name or licence. For image processing Pages uses libvips under the GNU LGPL, with a link to the source code of each version, and you may replace these libraries with a modified version. Pages contains no components under the GPL.
Pages goes online to the shop for the licence, updates, the docs and the theme gallery, to Anthropic or through your Claude Code for the AI, and to your server for publishing. Your websites with their facts, photos and history stay in their folders on your computer.
What Free can do and what Premium adds, split into Localhost, Editor and Pages.
WebDonkey Pages builds websites in a chat, checks them and publishes them to your server. You pay by the number of websites.
| Feature | Free | Personal | Business | Studio | Agency |
|---|---|---|---|---|---|
| In every package, Free included All of this comes with Free too, for one website. | |||||
| Have your website built in a chat, with its own design | included | included | included | included | included |
| AI through your own Claude Code or an Anthropic API key, chosen per website, your client's key included | included | included | included | included | included |
| Live preview for desktop, tablet and phone | included | included | included | included | included |
| Photos by drag and drop, facts by form | included | included | included | included | included |
| Automatic checks after every change: accessibility, mobile layout, content and links; Lighthouse in the full check | included | included | included | included | included |
| History of up to 60 versions, back to any of them | included | included | included | included | included |
| Status per website: draft, open facts, published, update pending | included | included | included | included | included |
| Schema.org and llms.txt built in | included | included | included | included | included |
| Legal notice and privacy policy as sample texts from your details, to be confirmed before publishing | included | included | included | included | included |
| Website in German or English | included | included | included | included | included |
| Subpages per website | unlimited | unlimited | unlimited | unlimited | unlimited |
| ZIP export | included | included | included | included | included |
| Back up a whole website as a ZIP and import it, on another Mac too | included | included | included | included | included |
| Archiving frees the slot, nothing gets deleted | included | included | included | included | included |
| Take over an existing website from the Page Builder Toolkit | included | included | included | included | included |
| Test locally in WebDonkey, messages from the contact form land in Mailpit | included | included | included | included | included |
| Runs without WebDonkey | included | included | included | included | included |
| Signed app updates through the shop | included | included | included | included | included |
| Where the packages differ More websites, direct publishing and the bundle price with WebDonkey Premium. | |||||
| Active websites | 1 | 3 | 3 | 10 | 30 |
| Account type | any | personal | business | business | business |
| Add-on with 5 websites | not included | not included | included | included | included |
| Publish straight to your server over SFTP: full check first, only changed files, then the live page is fetched | not included | included | included | included | included |
| Prepare the server: Caddy with HTTPS through Let's Encrypt on Debian or Ubuntu | not included | included | included | included | included |
| Use servers saved in WebDonkey | not included | with WebDonkey Premium | with WebDonkey Premium | with WebDonkey Premium | with WebDonkey Premium |
| No “Built with WebDonkey Pages” note in the footer | not included | included | included | included | included |
| Submit your own app themes to the gallery | not included | included | included | included | included |
| WebDonkey Premium | not included | cheaper as a bundle | cheaper as a bundle | booked separately | booked separately |
| Link to your WebDonkey licence, one key for everything | not included | included | included | included | included |
Active websites count, drafts included. If you cancel or move to a smaller package, nothing is lost: websites above the quota are locked, and export always stays possible.
Requirements: macOS 11 or later, Node.js 22.12 or later (not included), Google Chrome for the checks and Claude Code or an Anthropic API key.
After the purchase your Pages key sits in your customer account under “My WebDonkey licences”. Four steps and your plan is unlocked in the app.
If you have coupled your Pages licence to a WebDonkey licence in your customer account, your WebDonkey key works here just the same. Both apps then share one seat, and on the same Mac they count as one device. If Pages is connected to a running WebDonkey that holds a different key, Pages offers to take it over. If a key has no Pages plan in it, Pages says so and runs as Free.
Yes. A Pages licence comes with a key of its own. In your customer account under “My WebDonkey licences” you couple it to one of your WebDonkey licences. From then on your WebDonkey key works in Pages too, and the Pages key keeps working. Both apps then share one seat; on the same Mac they count as one device. Each licence keeps its own term and subscription. Coupling never happens automatically, and you can undo it in your account. Coupling and undoing count towards the same limit of three changes in 30 days. In a company account the buyer couples; a licence shared with staff takes its coupled products along.
Pages is billed by the number of your websites. Personal (for private customers) and Business (for companies) include 3 websites each, Studio 10 and Agency 30. To the company plans Business, Studio and Agency you add add-ons of 5 websites each whenever you need them; if the plan ends and an add-on runs longer, it becomes a licence of its own that you assign to a running company plan or cancel (after a full refund, chargeback or termination for good cause it ends as well). For more than 50 websites we make you an individual offer. All plans are subscriptions: Personal monthly, the company plans monthly or yearly; a year costs ten monthly payments. No Pages plan includes WebDonkey Premium; Personal and Business are cheaper in their first term together with WebDonkey Premium. Without a licence Pages runs as Free with one website: building, checking, backing up and the ZIP export work in full, and the exported website then carries the note “Built with WebDonkey Pages” in its footer. Publishing straight to your server, testing the connection and preparing the server start with Personal.
What counts are your active websites, that is every one that is not archived. Drafts and imported websites count too, subpages of a website are not limited. When you archive a website, Pages puts its last build as a ZIP into its folder, its data and history stay there, and its place in the quota becomes free. As soon as a place is free again you reactivate it, nothing has to be deleted. If you move to a smaller plan or your subscription ends, nothing is lost: the websites created first stay active (an imported one counts as newly created), the rest are locked. Locked websites can still be viewed, exported, backed up and archived, just no longer edited, checked or published.
Start free. Go Premium when you need more. WebDonkey sets up web servers, databases, real HTTPS and every tool right on your Mac, without you touching a single config file.
macOS 11 or later, on Apple silicon and Intel.
Do you like cookies?
The technically necessary cookies are already on board. Statistics (Google Analytics) and ad measurement (Meta, TikTok) only if you agree. Your choice applies here and in the shop at shop.webdonkey.io; you can change it at any time under “Cookie settings”. What I collect