Which pages can Dreamfare actually read?

Any public web page it can fetch as HTML: personal blogs, free newspaper articles, hotel neighborhood pages, public docs. It follows redirects, reads up to a size limit and refuses files that are not web pages. If a page needs a login, it cannot be fetched, and Dreamfare tells you rather than charging you to find out.

What about paywalled articles?

Only the part that loads for a logged-out reader is available, which is usually the introduction. If you are a subscriber, the reliable route is to copy the article text and paste it in as text. That path reads exactly what you paste.

Can I paste text instead of a link?

Yes, and it is often the better option. Anything from about forty characters up works: an article you copied, a friend's email, your own notes, the itinerary a colleague sent. The same reader finds the places in it.

Does it copy the writer's article into my trip?

No. What lands in your trip is the places the article names, matched to real venues, plus a short note of the practical advice and a link back to the source. The article stays where it was published.

Will it invent places that are not in the guide?

The import only files what the page names, and a name that does not resolve to a real venue near the destination is dropped rather than pinned somewhere plausible. Filling the gaps between them is a separate step you ask the planner for.

How long does it take?

A normal article takes under a minute. You watch it fetch, read and build, and if the page turns out to be unreadable the import fails cleanly and gives back what it charged.

Travel guide to itinerary

Travel Guide to Itinerary: Turn Articles Into Trips

Paste a travel guide or blog post into Dreamfare and turn its recommendations into an organized, bookable itinerary.

One free import. No account needed. Your results stay here for 7 days.

Faroe escape

3 days · 2 travelers

Day 1Day 2Day 3

Sørvágsvatn rim walk

09:00 · Miðvágur

Múlafossur waterfall

13:30 · Gásadalur

Tórshavn old town

18:00 · dinner at the harbor

Hotel Føroyar

2 nights · Tórshavn

Illustrative app preview

The problem

Guides are written to be read once, not used for a week

A good city guide is eleven recommendations wrapped in two thousand words, ordered for the reading and not for the walking. Using it means twenty-six open tabs, a note with half the names spelled wrong, and the slow discovery that two of the restaurants are closed on the only night you are free.

How it works

Paste, read, plan

1
Paste the link
A blog post, a newspaper roundup, a hotel's own neighborhood page, a shared doc. If it is a public web page you can open, paste it.
2
Dreamfare reads the prose
The page is fetched and stripped down to its words, then read for venue names, neighborhoods and the advice attached to them.
3
Places, then days
Names are matched to real venues with addresses and filed into a folder. Ask the planner to spread them across the days you have.

Being straight with you

What imports well, and what does not

Some pages simply cannot be fetched by anything that is not signed in as you. Rather than let you find that out one failed import at a time, here is the honest split, and the paste-the-text route that covers everything in the right column.

Works

Personal travel blogs and Substack posts
Newspaper and magazine city roundups that are free to read
A hotel or restaurant group's own neighborhood guide
Public Google Docs, Notion pages and shared notes
Reddit threads, when Dreamfare has a route to Reddit
Your own notes, pasted as text instead of a link

Does not, or not fully

Pages behind a paywall give up only the part you can read logged out
Anything that needs a sign-in cannot be fetched at all
PDFs and files that are not web pages are refused rather than half read
Pages that render entirely in the browser can come back thin
Very long pages are read up to a limit, not indefinitely
A guide that names no venues produces no places, and says so

For every case on this side: select the article text, copy it, and paste it into Dreamfare as text. The reader is the same one a link goes through, and it reads exactly what you gave it.

A real example

A seven-day Japan guide, unpacked

A long two-city guide: four days in Tokyo, three in Kyoto, dozens of names threaded through the prose. The import pulls out the places and the practical lines attached to them, then the planner spreads them over the days you actually have.

Extracted from the article

TsutaSugamo, Tokyo
The guide's ramen pick. Ticket system, go before eleven.
4.1 on Google
Yanaka GinzaTaito, Tokyo
Old shopping street the article uses as its slow morning.
Nishiki MarketNakagyo, Kyoto
Named as the Kyoto food stop, with a warning about eating while walking.
4.3 on Google
Fushimi Inari TaishaFushimi, Kyoto
The guide insists on before seven in the morning or after eight at night.
4.7 on Google

Restaurants, neighborhoods and attractions, each with the writer's own advice kept alongside.

Spread across seven days

Day 2

Tokyo, north and east

09:00Yanaka GinzaSlow morning, the article's opening walk
11:00TsutaRamen, ticket machine, arrive early
20:00Hotel in NihonbashiFour nights, breakfast includedBook

Day 5

Kyoto, first full day

06:40Fushimi Inari TaishaThe early slot the guide argues for
11:30Nishiki MarketStanding lunch, do not walk and eat
15:00Kyoto walking tourAdded from activity search, free cancellationBook

Days two and five of seven. The early-morning shrine slot is the guide's advice, kept.

What you end up with

The useful half of the article, in a form you can use

The recommendations, separated from the prose
Two thousand words become the eleven places the writer actually recommended, each with its neighborhood, so you can see the shape of the guide at a glance.
The advice travels with the place
Closed Tuesdays. Cash only. Book two months ahead. The sentence that made the place worth going to is kept next to it instead of scrolled past.
A map instead of a reading order
Guides are written in the order that reads well. Once the places are pinned, the ones that belong to the same afternoon become obvious.
Several guides, one library
Import three articles about the same city and they collect in one place, duplicates and all, so you can see which spot every writer agrees on.
Still your itinerary
Rename stops, move them between days, delete the two you were never going to do. The import is a starting point, not a contract.
A link back to the source
Each place keeps the article it came from, so you can reread the paragraph rather than trying to remember which of the four guides said it.

Compare what three writers agree on

Import several guides for the same city and the overlaps do the work for you. The restaurant every article names is a safer bet than the one that appears once, and you can see that in a list rather than by remembering.

Then fill in the gaps

A guide rarely covers everything. Ask the planner for the missing evening, search stays and activities with live prices, and attach the ones you pick to the right day with a booking link on the stop.

How the AI itinerary planner works

Questions people ask

Which pages can Dreamfare actually read?: Any public web page it can fetch as HTML: personal blogs, free newspaper articles, hotel neighborhood pages, public docs. It follows redirects, reads up to a size limit and refuses files that are not web pages. If a page needs a login, it cannot be fetched, and Dreamfare tells you rather than charging you to find out.
What about paywalled articles?: Only the part that loads for a logged-out reader is available, which is usually the introduction. If you are a subscriber, the reliable route is to copy the article text and paste it in as text. That path reads exactly what you paste.
Can I paste text instead of a link?: Yes, and it is often the better option. Anything from about forty characters up works: an article you copied, a friend's email, your own notes, the itinerary a colleague sent. The same reader finds the places in it.
Does it copy the writer's article into my trip?: No. What lands in your trip is the places the article names, matched to real venues, plus a short note of the practical advice and a link back to the source. The article stays where it was published.
Will it invent places that are not in the guide?: The import only files what the page names, and a name that does not resolve to a real venue near the destination is dropped rather than pinned somewhere plausible. Filling the gaps between them is a separate step you ask the planner for.
How long does it take?: A normal article takes under a minute. You watch it fetch, read and build, and if the page turns out to be unreadable the import fails cleanly and gives back what it charged.