Skip to content
Interface language: English
Design / Signal

PDF or web page? How to share an offer people can actually read

Choose PDF, HTML or both with purpose. Consider accessibility, updates, sharing an offer, document versions and a practical plan for checking the file.

Article language: English

In a garden at night, a woman examines an illuminated white petal beside a sleeping cat.
In this article

An offer may look like a million dollars in a PDF, yet on a phone the customer sees it through a virtual keyhole. That is a good reason to compare formats. An HTML page usually makes reading, updating and getting in touch easier. A PDF is useful when someone needs to keep, share or print a particular version. You can offer both, provided the company knows which material contains the current offer.

Do not start with the cover. First establish the task: learning about a service, comparing terms, saving instructions or working on a document within an organisation. The same material can make a beautiful presentation in a meeting and an awkward way to find one fact on a bus. The format should help the reader complete the task, not make them change their plans.

Ask four questions before commissioning a document

First, where will readers come from and what will they use to read it? A link in a message may be opened on a phone rather than the author's large screen. Second, how often will the content change? An offer that is updated needs different maintenance from a report recording a closed period. Third, does someone need to retain a specific version? Fourth, what should they do after reading?

A hypothetical training studio might need a current page describing a workshop and a separate downloadable programme for a particular session. The page answers questions from new readers; the document lets someone share the agreed programme with a manager. The two formats serve different purposes and need not have identical layouts.

A service guide is another case. If the steps change regularly, a file saved six months ago may mislead. Publish the current instructions online and show the date and a way to check for updates on the downloadable version. A need to download does not always mean content should be frozen in time without warning. For a product, prepare the right version, steps and a way to recognise the result, regardless of the publication format. The guide to a product’s first use (in Polish) discusses these choices.

Record the initial choice alongside the service page layout. The guide to a B2B service page (in Polish) discusses the scope and next step the page should explain. A file should not take over the whole answer simply because it already exists in a company folder. Key information about fit, scope and the next step belongs where the customer starts reading.

What a web page offers, and what it does not solve automatically

HTML is the format used to build ordinary web-page content. It makes it easier to adapt text to screen width, navigate and connect related material. A well-prepared description can lead directly to the scope of a service or a form. The reader need not open another tool just to read two paragraphs.

The Government Digital Service recommends publishing in HTML where possible, citing, among other things, the reader's browser settings and difficulties with other formats. This is guidance for a British public service and a useful design reference. It is not an automatic assessment of every Polish company's obligations.

HTML alone does not prove accessibility. A page with poor contrast, chaotic headings or hidden text can still be hard to read. The format choice should lead to testing actual use, not to putting a magic word in a report. Basic checks are discussed in the guide to business website accessibility (in Polish).

A web page also needs an owner and update rules. If every department changes its own description, a reader may encounter contradictory terms in two places. Easy publishing does not remove the need for editorial order. A format can solve some reading problems, but it cannot assign responsibility for content on its own.

When a PDF adds concrete value

A PDF can convey a document with a defined layout and preserve a version. That can help with material to discuss at a meeting, an event programme or a report shared within an organisation. The condition is simple: keeping the document should be part of the reader's task, not merely the publisher's habit.

Before production, ask whether every page's appearance needs to be controlled or whether the content simply needs to be downloadable. If the goal is only to save the essential information, a well-prepared print version may be enough. If a consistent document with attachments, page numbers and an identifiable version is needed, a separate file may be justified.

A PDF does not have to be a scan or an image of text. When designing it, retain real text, working links and a meaningful structure. A visually appealing multi-column layout needs an additional reading-order check. A reader should not hear alternating fragments of two separate paragraphs merely because they look attractive on screen.

Do not put everything the company knows into one heavy catalogue. An offer file should answer a specific need. Otherwise the customer also downloads sections they do not need, and the author updates the whole publication when one sentence changes. A catalogue can be impressive without needing its own tour guide.

Document structure begins before export

In a word processor, use proper heading, list and table styles. Making a sentence bold does not make it a heading in the file's logical structure. An organised source makes later checks and corrections easier, although it does not guarantee that export will preserve everything correctly.

W3C technique PDF3 addresses correct reading and keyboard navigation order in tagged PDFs. It also explains the role of the tag structure. This is a supporting technique, not a standalone accessibility certificate. Its practical point is simple: reading order must match the meaning of the content.

During acceptance, test navigation through headings, reading a table, descriptions of meaningful images and functioning links. Selectable text is a good start, but not a complete test. In documents with sidebars, in particular, check that an explanation reaches the reader beside the relevant passage rather than only at the end.

Keep the editable source along with export instructions. If every small change requires rebuilding the design from the finished PDF, update costs rise and corrections are more likely to be postponed. Someone who was not present for the original layout should be able to maintain the document.

Aeneia conceptual photography

Two formats need one update process

If an offer exists as a page and a PDF, identify the source on which updates are based. It might be a publishing system or an organised source document. The editor should not have to remember three copies hidden in different folders. Memory helps, but it cannot replace a version register.

For each significant change, check the title, scope, terms, contact details and links in both formats. Record what to do with the old version too. Sometimes it needs to be kept as an archive; sometimes it should be withdrawn from the current offer. There is no single right decision for every document: it depends on its role and previous use.

Give the file an identifiable name, version or date, and an address for current information. “Offer_final_really_final_7” says a lot about its author's feelings and little about its content. The name shown on the page should also explain the format and file size so readers know what they will open and whether to download it on a slower connection. If there are several documents, plan a library showing each file's version and purpose so readers can identify the right one before opening it. The guide to a download centre (in Polish) explains how to organise those details.

Include file updates in the CMS publishing process. The guide to publishing content in a CMS (in Polish) describes roles, approval and checking the public result. Review must not stop at the descriptive page. If the link still leads to old terms, the new text does not complete the change. Check the downloaded material itself too.

Keep track of documents when changing sites and languages

A file address may live long beyond the page: in messages, presentations and customers' internal systems. When rebuilding a site, include such addresses in the migration map. The guide to preserving addresses during migration (in Polish) explains how to assess old file addresses. Moving a file directory without checking links can invalidate material editors no longer see on the current site.

Do not replace any old file with the latest one simply because it has a similar title. Someone may have referred to a particular version of a programme or report. First establish the document's meaning, then decide how to redirect or archive it. The explanation of the change should make sense to someone who does not know the site's history.

In language versions, adapt the file content as well as the link name. A Polish title above an English document needs a clear language label. If a version does not yet exist, say so rather than directing readers to a random resource. The relationships between addresses and switching are covered in the guide to reviewing multilingual website versions (in Polish).

When translating a document, check its layout again. Longer sentences may push captions and explanations onto the next page. This affects not only appearance but also understanding tables and reading order. A sound language version requires reviewing the actual file, not merely approving translated text.

Explain the download before someone opens it

A label saying only “Download” does not tell readers whether they are getting a workshop programme, the whole company catalogue or a document template. Give the link a specific name and briefly explain what is inside. If the content has a date or version, show it nearby. Readers should be able to judge usefulness without downloading several similar files on trial.

Also state the language if it differs from the page. Give the size for a larger file. For a form to be edited, explain whether it must be completed in software, printed or handled another way. Some frustration comes from a lack of warning rather than the document format itself. A clear description helps people choose how to work.

Do not make an embedded preview the only way in. Check that there is an ordinary document link and that the key information is available without a convenient preview in a particular browser. The author's computer does not represent every reader's device. Test on a phone and with text enlargement settings people actually use.

If the document is longer material to prepare for a conversation, explain which parts to read first. You need not summarise every paragraph separately. It is enough to indicate the purpose, scope and intended use. The file becomes a tool for the task rather than a polite obligation everyone plans to read later.

Check the path back to the conversation too. Does the saved document have a current contact address? Do its links still work outside the page? Does the printout identify the company and document? A file may circulate independently, so it needs a minimum of context that does not depend on having the website open beside it.

Test both formats against one task

Include a situation where the author is unavailable. Give the file to someone who did not attend the meeting and ask them to identify its purpose and the current terms. Do not supply the missing context. If they must call to establish the basic scope or version, the document needs more information, even if everything was clear during the presentation.

Separately, test the choice between formats. Can the user see that they can read the offer online or download a particular version? Do the two link names explain the difference? The downloadable version should add convenience, not force people to guess which of two similar items is correct.

Choose three specific questions: what does the service include, what must the customer prepare, and how can they start working together? Try to find the answers on a phone, a large screen and in the downloaded document. Do not assess only the overall impression. Record where you have to zoom, go back, guess or search for an inactive link.

When comparing offers, check that both versions preserve the terms and relationships between data. Mobile comparison tables need a different layout from print but should convey the same meaning. The guide to comparison tables on a phone (in Polish) considers how to preserve those relationships. Losing an awkward footnote in export is not simplification; it changes the content.

Finally, ask someone uninvolved in preparing the material to pass it on and identify the current version. This small test will show whether the document still works outside the context of the page. If a saved file does not say who issued it or where to find updates, improve it before sharing it widely.

If you want to organise your online offer and downloadable materials, see the Aeneia Design services.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear