Upload a file or build in an editor

If you already have the page, an editor is a machine for retyping it. If you do not, an uploader has nothing to take.

These two kinds of product are compared constantly and they solve opposite problems. One question settles it.

A file being dropped to publish, beside a template editor building a page from scratch.
A file being dropped to publish, beside a template editor building a page from scratch.

Does the page already exist

Yes. You have a file, exported from something, generated by a model, or written by hand. An uploader takes it and gives you an address. The page you get is the page you made.

Putting that file into a builder means opening an editor and recreating it inside their template system. The result is approximately what you had, in their structure, and the original file is now irrelevant.

No. There is nothing to upload. A builder gives you a template, a drag-and-drop editor and something live in twenty minutes with no technical knowledge.

An uploader is useless here. It is a delivery mechanism, not a creation tool.

You have a file You have nothing
Uploader Correct Nothing to upload
Builder Rebuild it in their editor Correct
Time to live Seconds Twenty minutes
Page belongs to You, as a file Their editor

What you keep

This is the difference that matters in two years.

An uploaded page is a file. Move to any other service, upload the same file, and it is identical. The service is replaceable and you lose nothing.

A built page is a design inside a product. There is no file. Exports exist and produce generated markup that is unpleasant to edit, so in practice moving means rebuilding.

Neither is wrong. It is worth knowing which one you are choosing.

An uploaded page's source file beside a builder's generated export markup.
An uploaded page's source file beside a builder's generated export markup.

Several pages

Uploaders generally take a folder, so a small site with relative links between pages works as it did locally.

Builders vary. Some are single-page by design, and multi-page is frequently behind the paid tier.

If you have a folder already, that settles it too.

The domain is the same either way

Whatever you choose, put your own domain in front of it.

The page can be rebuilt. The address cannot, because it is in messages, printed material and other people's pages. With your own domain, changing your mind costs an afternoon rather than every link you have published.

For the surrounding ground, see Choosing a Tiiny Host alternative and Choosing a Carrd alternative.

Put it at an address

Ask whether the page already exists. If it does, upload it. If it does not, build it. Keep the file either way, and own the domain regardless.

Then the tool matches what you actually have.

Questions people ask

What actually separates these two kinds of tool?

Where the page comes from. An uploader takes a file you already made. A builder produces one from a template, which means the page lives inside the product.

I have an HTML file already. Which one?

An uploader. Putting an existing page into a builder means rebuilding it in their editor, and the result rarely matches what you had.

I have nothing and cannot write markup. Which one?

A builder. It gets something live this afternoon with no technical knowledge, which an uploader cannot do because it has nothing to upload.

Which one can I take with me?

The file. An uploaded page exists as a file you keep. A built page exists as a design in somebody else's editor, and the export is usually generated markup.

Does either handle several pages?

Uploaders take a folder, so several pages with relative links work. Builders vary, and multi-page is frequently a paid feature.

Keep reading