Word to Website · Your App Cloud
Turn a Word document into a website
Upload the document and choose which headings become pages. Give each page a title, a description and a next step, then check links, pictures and the phone layout before you publish.
From a document read top to bottom to pages people land on.
Choose the pages, write what each one says in a search result, then read the site the way a stranger would.
01
Decide which headings become pages
Attach the Word file with the upload button above. In the prompt, name the pages you want, such as Home, Services, Pricing and Contact, and the heading each one starts from. Say which sections stay out, like a revision table or internal procedures.
02
Write each page's title, description and next step
A document is read from its first page. A visitor may reach Pricing from a search result and never see your introduction. Give every page a short title, a one-sentence description and the one thing a reader should do there.
03
Check links, pictures and the phone layout
Try the preview on a narrow screen, the width of a phone. Follow every link, read each picture's alt text and look for leftovers such as 'see page 4'. Publish, open the address on your phone, then send it to someone who has never read the document.
What each part of the document becomes.
Read across each row: the part you know from Word, where it can go on the site, and how to confirm it. The quoted text is a made-up sample from a landscaping business in Sacramento.
| In your Word document | On the website | What to check |
|---|---|---|
| Heading 1 text, such as 'Our Services' or 'Service Area' | A page of its own, and an item in the menu | Count the Heading 1 entries in Word's Navigation pane and the items in the site's menu. Check that the two numbers match, unless you merged or dropped a page on purpose. |
| Heading 2 and Heading 3 under each of them | Sections with subheadings on that page | Scroll the longest page on a phone. If you lose track of where you are, split it into two pages with their own menu items. |
| The opening paragraph: 'This document describes the services offered by Clarke Landscaping' | The home page introduction: who you serve, what you offer and one next step | Read the first screen of the home page on a phone. Check that it says what you do and where, without the words 'this document'. |
| The file name, such as 'Services_v7_FINAL.docx' | A title and a description written for each page: the words a browser tab shows and a search result can use | Open each page and read the title in the browser tab. Check that no two pages share a title and none repeats the file name. |
| Photos pasted into the text, such as finished garden projects | Images on the page, each with alt text that says what it shows | Check that each photo you want is on the right page and that you have the right to publish it. If one is missing or looks soft on a wide screen, supply the original photo instead of the copy resized in Word. |
| A table of prices or seasonal hours | A table or a short list on the page | Wide tables often run off a phone screen. Look at each one there, and ask for a list wherever you have to scroll sideways. |
| Hyperlinks, and cross-references such as 'see page 4' or 'see Pricing below' | Links to the right page on the site | Follow every link in a private browser window. A link to a file on your computer, or to a shared drive or SharePoint folder only your team can open, won't work for visitors. |
| The header, footer, page numbers, table of contents and a 'Draft' watermark | Left out. The menu and a site footer with your contact details take their place | Use your browser's find on each page to look for 'Page 1', 'Draft' and 'Confidential'. Remove any hit that only made sense on paper. |
| The contact paragraph at the end: 'Call Emma Clarke at (916) 555-0142' | A Contact page, and a button that leads to it from every page | On a one-page site, the button can link to your email address or phone number. A form that saves requests or emails them to you needs a backend. Send yourself a test request either way. |
What the document was written for.
A Word document is built for paper and for readers who start at page one. A website is read in pieces, often on a phone, by people who don't know you yet. Prepare a copy of the file with that in mind before you upload it.
Headings that are only bold text
In Word for Windows, choose View, then Navigation Pane, or press Ctrl+F, and open the Headings tab. It lists only text styled as a heading, and skips headings inside tables, text boxes, headers and footers. Restyle the missing ones, or name them in the prompt.
Tracked changes, comments and hidden text
Switching to No Markup only hides tracked changes, so accept or reject each one before you upload. Then run File, Info, Check for Issues, Inspect Document on a copy. It finds comments, hidden text and properties such as the author's name.
Details meant for colleagues
Staff cell numbers, supplier costs, 'price TBD' and notes in square brackets belong in an internal file, not on a public page. Delete them from the copy you upload rather than hoping to spot them on the site.
Paragraphs written for paper
A paragraph that fills half a printed page turns into a long scroll on a phone. Mark the ones to split. If you ask the building assistant in Studio for shorter versions, compare each with your original and keep only what is still accurate.
An illustrative starting point
A small site cut from your document.
Pages from your Word headings, a menu to move between them, and a title, description and next step on every page.
Pages from your headings
Each Heading 1 you pick can become a page, with its Heading 2s as sections. Someone looking for prices then opens Pricing instead of scrolling through a twelve-page file.
A menu instead of a table of contents
A menu of short page names, such as Services or Service Area, takes the place of the contents list and page numbers. Check that the menu fits a phone screen without wrapping onto several lines.
A title and description for each page
Written for that page rather than taken from the file name. A browser tab shows the title and a search result can use both, so each one should say what its page covers.
A next step where reading ends
Call, email, book or ask for a quote: one action per page. A link to your email address or phone number works on a one-page site. A form that saves each request, or emails it to you, makes the site an app with data.
Together in your app cloud
The pieces behind the possibility.
Choose the models and services that support the experience you want to create.
File storage
A home for your documents and media
Email
Keep conversations moving
Security
Secure every connection
A little more context
Good questions.
Is this just my Word document posted online?
No. Posting the file makes visitors download it and read from page one. Here the document is the source for separate pages, a menu and a next step on each page. You decide what each heading becomes and leave out what only made sense on paper, such as the cover page.
Can I publish the website on the Free plan?
Yes, as a one-page site that only presents your content, with each Heading 1 as a section of the page, on an Exepad address. Several pages at their own addresses, a contact form that saves requests, an area people sign in to or email sent by the site make it an app, which needs a paid plan to go live.
Can the website use my own domain?
Custom domains come with Pro. If your letterhead or the document's footer already prints a web address, connect that domain before sharing the site so print and web agree. When the domain also carries your email, add only the records Studio shows and leave the email records alone.
Will the pages show up in Google?
No one can promise that; Google decides what it shows. You control what it reads: a distinct title and description on each page, headings styled as headings, and words typed as text rather than a picture of a page. Build each page around a question people actually search for.
What happens to the pictures in my document?
Check each one on the site rather than assuming it came through. Confirm it sits on the right page, that you have the right to publish it, and that its alt text describes it for people who can't see it. A photo resized in Word may look soft on a large screen, so keep the original at hand.
How do I update the site when the document changes?
Editing the Word file changes nothing on the site, because an upload is a snapshot. For a small change, edit the page in Studio and publish again. For a new edition, upload the revised document on purpose and compare the pages before publishing. Decide which one is the master copy from now on.
Can the person who wrote the document help keep the pages current?
Studio has one builder per Exepad account, so collect the changes from the office manager who maintains the services document today and make them yourself. If the pages change often, describe an editor's sign-in so they can update them in the published site. If an edit goes wrong, use the versions available in Studio, inspect the restoration and publish after review.
Explore Pricing for plans, included capabilities, and usage details.
Keep exploring.
Start a website from an idea instead ↗
See the outcome and the capabilities behind it.
Turn any file into a website ↗
The overview of file-to-website guides, for when your material is a PDF, a slide deck, a spreadsheet or an image.
Understand data and context ↗
Give information the right place in your app.
Prepare to publish ↗
Check the experience you will share.
Your ideas, up and running
Your next idea has a home.
Build an app. Run an agent. Make it yours.
Start building