Archicad 28 Visualizer moves to English-only prompts

Teams scheduling an Archicad 28 visualization deliverable have a specific service deadline to check. Graphisoft's transition notice states that AI Visualizer 1.0 in Archicad 28 will stop generating images on 9 October 2026. The same notice says prompts have been English-only since 10 September 2026 because a supporting translation service is retiring. As reviewed on 1 October, the October shutdown remains a scheduled event. Graphisoft transition notice

The notice also announces AI Visualizer 3.0 for Archicad 29 and 30, linked to the Archicad 30 release. It describes an automatic service update for AI Visualizer 2.0 in Archicad 29. This article has not verified that rollout in a user account. A project team should confirm its actual access before assigning a deadline to the replacement.

Identify the dependency

GAD recommends listing the active projects that still depend on the affected service. For each, record the installed Archicad version, responsible person, next presentation date and whether fresh generated imagery is essential. Include work promised after the shutdown, even if the model itself is already complete.

This short inventory reveals where a visualization change might disrupt a deliverable. An old concept presentation with saved images presents a different task from a live workshop expecting several new options. Give those situations different plans rather than treating every project as an emergency software migration.

Preserve a useful comparison set

Save the accepted images, source views, model revisions, prompts and approval notes in the project record using the tools already available. Keep the English prompt beside the original-language brief where translation was involved. Have a bilingual team member check material terms and spatial descriptions that could change meaning.

Do not assume that the same prompt will reproduce the same image in another service or version. Set aside a representative, permitted test view with a few unmistakable features: repeated openings, a clear roofline and a known facade rhythm. Record which features must survive and which visual qualities the team is evaluating.

Test the replacement before scheduling it

Use a separate test copy and review the result against that baseline. Confirm that the responsible user can generate, save and retrieve an image through the proposed workflow. Inspect geometry, context and the interpretation of the brief. Record the time needed for correction and review, as well as generation.

An authoring-software upgrade may involve wider project coordination. Agree that step with the BIM lead and the people responsible for project compatibility; avoid making it an improvised fix immediately before a client meeting.

Define a fallback deliverable

Choose a presentation route the team can complete with verified access, such as saved approved imagery or an established rendering process. Tell the project lead which visual studies remain provisional. The readiness test is straightforward: a named person can produce the required output on the planned date, and the team can trace its design assumptions.