Document Agents
Turn a brochure, catalogue or report into a real, responsive website — not an embedded file.
Describe the document you want to convert — what it is, how it's organized, who it's for — and the agent restructures it as web pages: navigation from its sections, real text instead of images of text, tables that work on phones. Describe your PDF below to get started; you'll attach the file itself once you're in early access.
Try an example
Most businesses have a graveyard of PDFs doing jobs they were never designed for: menus that don't work on phones, catalogues customers must download to read, brochures that search engines can barely index. The PDF to Website Agent converts these documents into actual websites — pages with real, selectable text, a navigation built from the document's own sections, and layouts that adapt to any screen.
It's built for restaurant owners still linking a menu PDF, manufacturers whose catalogue is a ninety-page download, nonprofits publishing annual reports, and any team whose best content is trapped in a format made for printers. If the document was worth designing, the content is worth publishing properly.
Start by describing the document below: what kind it is, how many pages, how it's structured, and anything that needs special handling — price tables, image galleries, footnotes. When you're in early access, you'll attach the PDF itself, and the agent extracts its sections, headings, tables and imagery, then rebuilds them as web-native content.
The output is not the PDF displayed in a viewer. A landscape table becomes a responsive one; a multi-column brochure layout becomes stacked, readable sections; the document's chapter structure becomes the site's navigation. Everything lands in a Dual7 project as editable content — update a price in one place instead of re-exporting a new PDF every quarter.
Extraction from real-world documents isn't perfect, so review the converted content against your original before publishing — prices, dates and fine print especially. When the site matters to the business, you can take it through Dual7's governed pipeline: seven gated stages with human sign-off before anything goes live on your domain.
Text becomes selectable, searchable and indexable — visitors read it in the browser instead of downloading an attachment.
PDFs pinch-zoom; websites reflow. Menus, catalogues and reports become readable on the devices customers actually use.
Chapters, categories and sections become menus and page hierarchies, so long documents become browsable sites.
Change a price, an item or a date directly in the project — no designer, no re-export, no 'menu_final_v3.pdf'.
Web pages with real text, titles and descriptions can be indexed and ranked in ways an uploaded PDF rarely is.
The converted site can add what paper can't: enquiry forms, search, filters, and links that actually go somewhere.
The site is standard code and content in your project — publish to your domain, self-host, or hand it off.
What it is, its length, how it's structured, and what needs care — pricing tables, imagery, legal footnotes.
Once you're in, the agent extracts sections, headings, tables and images from the file itself.
Check the converted content against the original — especially numbers and fine print — and adjust layout or wording.
Ship the site from your project, then update it directly instead of ever re-exporting the document.
Headings, chapters and categories are detected and become the site's page hierarchy and navigation — the document's own outline, made browsable.
Spec sheets and price tables are converted into responsive HTML tables or cards that work on narrow screens, not frozen images of grids.
Multi-column brochure spreads become stacked, readable web sections that follow the source's visual hierarchy without copying its page geometry.
Photos and graphics from the document are extracted and placed in the new layouts, ready to swap or optimize.
Everything lands as editable text and structured content in your project — corrections and seasonal updates happen in place.
Add enquiry forms, click-to-call buttons, search or category filters to the converted content — features a static file can't offer.
The document's sections rebuilt as browsable pages for desktop, tablet and phone.
Menus and page hierarchy generated from the document's chapters and categories.
Real text, headings and responsive tables replacing the print layouts.
The document's photos and graphics placed in the new design.
Titles, descriptions and semantic structure so the content can be indexed.
All of it as a Dual7 project you own and can update, extend or export.
Example output
Input: a wholesale lighting supplier's catalogue PDF — six categories, spec tables per product, landscape spreads. Output: a site with category navigation matching the catalogue's structure, each product on a card with its spec table rebuilt responsively, an enquiry form per category, and a search bar the PDF never had. Price updates now happen in the project, not in a re-export.
An owner turns the menu PDF into a mobile-friendly page that customers can actually read at the table — and updates specials without a designer.
A manufacturer or wholesaler converts the annual catalogue into a browsable, searchable product site with enquiry forms per range.
A nonprofit turns its report PDF into an accessible summary site donors can browse, instead of an attachment nobody opens.
A services firm converts its sales brochure into a landing page with a working contact form, so the brochure's pitch can finally collect leads.
An agent converts a listing brochure into a property page with galleries, floor-plan sections and a viewing-request form.
An organizer turns the printed program into a mobile schedule attendees can browse instead of a PDF that renders sideways.
A freelancer or agency publishes its rate card as a clean page it can update quarterly without touching layout software.
An ops team converts a manual into an internal site with chapter navigation, easier to search than scrolling a document.
Menus, wine lists and event brochures are the classic trapped PDFs — and the highest-traffic pages a venue has.
Spec-heavy catalogues become browsable product libraries with enquiry paths attached.
Listing brochures and development documents convert into property pages that collect viewing requests.
Annual reports, impact documents and program guides become accessible public sites supporters actually read.
Programs, floor plans and exhibitor guides work better as mobile sites than as downloads.
Capability statements and service brochures become landing pages with working contact routes.
You provide
Our restaurant menu PDF — three courses, drinks list, allergen footnotes
The agent
The agent extracts courses and items, rebuilds the layout as a single scrolling page with section anchors, and formats allergen notes as a clear legend.
You get
A mobile-first menu page with jump links per course, readable prices, and an owner who updates specials in the project instead of re-printing.
You provide
Annual report PDF, 30 pages — we want a public summary site for donors
The agent
The agent pulls the report's sections — letter, highlights, financials summary, stories — and structures them as a small site with chapter navigation.
You get
A browsable report site with real text, key figures presented as web content, and a donate link that was impossible in the PDF.
You provide
Lighting catalogue, ~80 SKUs in six categories with spec tables
The agent
The agent converts categories into navigation, products into cards, and landscape spec tables into responsive layouts.
You get
A searchable catalogue site with an enquiry form per category — and a product team that edits specs directly.
You provide
Conference program PDF — schedule across three days, speaker bios, venue map
The agent
The agent restructures the schedule into day-by-day pages, bios into a speakers section, and the venue info into a practical-details page.
You get
A mobile event site attendees browse at the venue, updated live when a session changes rooms.
You provide
Property brochure for a five-bed listing — photos, floor plans, features list
The agent
The agent builds a listing page with a gallery from the brochure's photography, floor-plan section, features, and a viewing-request form.
You get
A property page the agency links from portals, with enquiries landing in their inbox instead of a download counter.
| Aspect | With the agent | Manual process |
|---|---|---|
| How visitors read it | Reflowed web pages that fit any screen | A PDF download pinched and zoomed on a phone |
| Search visibility | Indexable pages with titles and real text | A file search engines handle poorly and users rarely find |
| Making updates | Edit content directly in the project | Reopen the design file, re-export, re-upload, re-link |
| Interactivity | Forms, search, filters and links can be added | Static by definition — even links break between versions |
| Accessibility | Semantic HTML screen readers can navigate | Tagged PDFs are rare; most are poor for assistive tech |
| Analytics | See which sections and pages get read | A download count tells you almost nothing |
| Conversion | Enquiry and booking forms sit next to the content | The brochure's pitch ends in 'call us' with no mechanism |
A chatbot needs you to copy text in chunks and loses tables and layout along the way. The agent works from the file's structure — sections, tables and images together.
Spec and price tables become responsive HTML tables, whereas chat-pasted tables arrive as broken plain text.
The document's chapters become a page hierarchy with menus — a structured site rather than one long page of extracted text.
The converted content lives in your project as structured content; corrections don't require re-running a conversation.
The result ships as a real site with hosting and an optional governed release path — not a file you still have to put somewhere.
Saying what it is — menu, catalogue, report — and how it's organized helps the agent choose the right site structure from the start.
Prices, dates, figures and fine print deserve a line-by-line review after conversion. Extraction is very good, but you own what you publish.
Documents exported from design software convert best. Scanned pages are images of text and may need manual correction.
Some print sections deserve merging, splitting or cutting online. Let the document's logic guide the site, not its page count.
Images embedded for print proofing are often compressed. Swap in the originals where you have them.
An enquiry form, a booking button or a search box is usually the entire point of moving to the web — include it.
The site doesn't have to replace the document everywhere. Link the PDF for visitors who genuinely want a printout.
The whole point is that updates are now easy — assign someone to keep prices, dates and details current.
It converts a document — brochure, menu, catalogue, report — into a real website: the content extracted and restructured as responsive pages with navigation built from the document's own sections. The result is editable web content, not a PDF embedded in a page.
Describe the document in the input above to begin — what it is, its length and structure. Once you're in early access, you attach the PDF file itself and the agent works from the actual document.
Yes. Dual7 is free during early access, with no credit card required — including conversion, editing and publishing.
The agent follows the document's visual hierarchy and applies your brand colors and type to the new layouts. Expect to review and adjust — print designs rarely translate pixel-for-pixel, and the web version is usually better for it.
Tables are rebuilt as responsive HTML tables or cards that work on phones. Because numbers matter, verify every price and figure against the original document before publishing.
Text-based PDFs — exported from Word, InDesign or similar — convert most reliably. Scanned documents are images of text; the agent can attempt them, but plan for manual corrections.
Yes — that's the main reason to do this. All content lands in your project as editable text and structured data, so updates happen directly instead of through a design tool and a re-export.
Converted pages get real text, titles, descriptions and semantic HTML, which makes them indexable in a way uploaded PDFs rarely are. Rankings themselves depend on many factors and can't be guaranteed.
Yes — enquiry forms, filters and search can be added to the converted content. These interactive upgrades are often the biggest win over the original document.
You do. The site is a standard, exportable codebase with your content — publish on your domain, self-host, or hand it to a developer to extend.
Dual7 Agents
Turn a brochure, catalogue or report into a real, responsive website — not an embedded file. Start with your own input — the output is an editable project you own.
500+ users in production · Kanan.co moved off Salesforce onto Dual7 in four months · 100% code owned
Dual7 · a product of AlgorithmShift · Build once. Own forever.