Moving your existing website to Kreova, photos and all
Most people who try Kreova already have a website. It might be a few static pages a friend made years ago, a template site that never quite fit, or a brochure site with a contact form that emails nobody. The question we hear is not "can you build me a site" but "can you take the one I have and make it better without me starting over".
As of today, the answer is yes.
What changed
The builder could already read a web page you pointed it at. What it could not do was bring the files across. If you asked it to rebuild your site, it would recreate the layout and the words, then reach for stock photos where your real photos belonged, and link brochures back to your old host. That is not a move. That is a lookalike with somebody else's pictures.
The builder can now download your site's own assets straight into your new project: photos, logos, PDFs, fonts, icons and video. Point it at your current site and ask it to move everything here, and it will read your pages, find the real image and document links, copy them into the project, and reference them from the rebuilt pages. Nothing points back at the old server, so when you switch it off, nothing breaks.
What a move looks like
Here is a real example from this week, a car dealership's site with eight vehicle pages and seven downloadable brochures.
- One request: "Copy my existing website into this project, including the real photos and brochure PDFs."
- The builder read the home page, found the brochures page and the site's configuration, and downloaded all eight vehicle photos and all seven brochures.
- Every image on the new site is served from the new site. Every brochure download works.
- The contact form now saves enquiries to a database you can see in your dashboard, instead of disappearing into an email address.
The whole thing took one build and one small fix afterwards, a popup that would not close.
A detail we are proud of
One of the dealership's photos had a .jpg name but was actually a WebP file. The builder's download tool checks what a file really is by reading its bytes, not by trusting its name, and refused to save the file under the wrong type. On the next try it saved it correctly as .webp. The same check means that if a link on your old site points at a page that no longer exists, the builder will not save that error page as a broken image. It will tell you the link was wrong and go looking for the right one.
The rules it works under
- It copies your own site, the one you point it at. It will not go wandering across the web collecting other people's files.
- Up to twenty files per request, ten megabytes each. Large sites are copied in a few rounds.
- Images, documents, fonts and media only. It never downloads code. Your new pages are written fresh, which is the point.
- Internal and private addresses are blocked, always.
How we know it works
Every capability we add goes through the same test: a real build, from cold, on a throwaway project, with the results checked by machine where a machine can judge and by a person where it cannot. The machine checks whether the build committed, whether it used the right tools, whether it invented a link that does not exist, whether every image is served from your site rather than someone else's. A person checks whether the result is a website you would actually put your name on.
This week that second check earned its keep. Two builds of the same site passed every mechanical check, and one of them was clearly better, because it explored the whole site rather than stopping at the first page. Numbers tell you a build did not break. Only a person can tell you it is good. We keep both.
Try it
Open your project, paste your current site's address, and ask the builder to move it here with the real photos and documents. Tell it what to keep and what to change. If something looks off, say so in the chat, the way you would to a person, and it will fix it.
Your old site got you this far. Bring it with you.

Comments
Loading comments…