How to Update Multilingual Tutorials After a Product Change
Last Updated
Jump to section
Jump to section
Share
Share
Share
AI Video Translator, Localization, and Dubbing Tool
Dub Online
Update multilingual tutorials by mapping the product change to each affected scene, then reviewing every published language version against the corrected source.
A button moves. A plan name changes. A setup flow gains a new step. Your English tutorial is easy to find, but its Spanish and Japanese versions may still teach the old workflow. Before generating another voice track, decide which parts of the lesson are still accurate.
Multilingual production already matters to paying users. In Perso Dubbing's paid cohort, 31.9% of 2,902 creators used two or more target languages between December 1, 2025 and August 31, 2026. This is usage on one platform, not a market estimate or evidence that multilingual publishing causes growth. Source: State of AI Dubbing 2026, Mid-Year Update.
The real example below comes from Perso Dubbing's November 2026 update to its product entry page. We compared the saved pre-change page with the current English, Korean and Spanish pages. The case shows how a new entry path changes what a tutorial must explain.
What needs to change in a multilingual tutorial?
Start with the instruction the viewer must follow. A correct translation can still direct someone to a button that no longer exists.
Product change | What to review | Likely action |
|---|---|---|
Color or spacing changes; the task is identical | Whether viewers can still identify the control | Keep the scene if it remains unambiguous; log the review |
A button or menu is renamed | Screen capture, narration, captions and each locale's actual UI label | Replace affected visuals and wording |
A step moves or a prerequisite is added | The complete task sequence and surrounding transitions | Record the revised task and review the full lesson |
A plan, permission or availability condition changes | Every scene and description stating the old condition | Correct the claim and verify the applicable audience |
Only a target-language translation is wrong | That language's script, audio and captions | Correct that version; check other versions for the same source ambiguity |
Keep a scene only when its instructions remain accurate for the product version your audience uses. If old and new interfaces coexist, label the tutorial's scope instead of silently replacing the only useful guide for an older version.
Build a change map before you dub again
Assign an ID to each task or scene. Connect it to the approved source script, visible UI labels and published language versions. Keep a copy of the previous source and exports so reviewers can see exactly what changed.
Verified example: the entry path now branches into desktop and online
Our saved pre-change page for Perso Dubbing's product home led with an online dubbing description and a free-trial action. By our November 11 check, the page presented a desktop download alongside a separate online action. The change was to the product entry guidance; this check does not establish when the desktop app itself first launched.
The current setup guidance adds requirements that an online-only tutorial cannot cover: a Perso account, a free API key when requested, a local voice model, and Hunyuan for local translation. It also distinguishes that translation route from ChatGPT, which uses the user's own account limits. Initial model downloads and computer-dependent processing are part of the setup.
We checked those setup conditions in the live English, Korean and Spanish page text. The English and Spanish entry controls were also checked in a browser. We did not install the app, generate a dub, or verify a finished localized tutorial.
For a tutorial starting on this page, the useful revision is a branch before the first click. An online lesson should identify the online action. A desktop lesson needs its own setup sequence. The following scene plan applies the verified change to an illustrative tutorial; it does not claim these video edits have already shipped.
Scene in the proposed revision | Keep or change | Evidence needed to approve it |
|---|---|---|
S01: choose the workflow | Replace the old entry capture; show which action the lesson follows | The displayed label and destination match the chosen route |
S02: prepare the desktop app | Add a desktop-only setup segment, including the account and model choices | A reviewer completes the shown setup on a supported computer; until then, mark the video segment unverified |
S03: upload and dub online | Retain only in the online branch after checking the current workspace | The recording still matches that workflow; desktop behavior is checked separately |
S04: explain the output | Review narration, captions and feature claims for the selected route | Every promise is supported for the demonstrated model and export |
The page change is verified. The scene plan is a recommended revision, with app execution still requiring its own check.
This distinction changes the release decision. A localized video can accurately translate the old narration and still omit a new setup requirement. Check the path the viewer must take before approving the wording.
Separate the scope of the edit from the scope of generation. A small script change does not guarantee that your selected dubbing tool or model can regenerate one sentence. If partial replacement is unavailable, generate a fresh version and assemble the approved material in your video editor.
Review the translated instruction against the screen
Give the language reviewer the new capture alongside the script. Ask them to follow the instruction as a viewer would.
If the product UI is localized, use the label shown in that locale. If the screen remains in English, preserve the English control label in the instruction and explain it in the viewer's language where needed. A dictionary translation of a button name can make the right control harder to find.
Maintain a small terminology table with the source label, each approved UI label, and any terms that must remain unchanged. Add version-specific names such as plan labels only after checking the current product.
With Perso Dubbing's video translation workflow, review the script and voice settings for each language before generating. Its product guidance explicitly warns against assuming that an edit in one language updates every existing version. Keep your release checklist outside that assumption.
For the initial production workflow, see our guide to localizing SaaS product demos. Use the update process here when the recorded product changes.
Check timing after the new wording is approved
Listen while watching the updated task. The instruction should arrive while the relevant control is visible, and the viewer should have time to recognize it before the next action.
If the translated line runs past the cut, first remove unnecessary wording without losing conditions. If it still needs more time, extend the screen hold or revise the edit. Speeding up the voice can make a setup tutorial harder to follow.
Check the boundary before and after the replacement: audio level, voice continuity, pauses and subtitle timing. Our product demo timing guide covers the initial synchronization problem; these same checks apply again after an update.
Keep a release record for every language
A finished source video does not establish that every localized export is ready. Use one row per destination language, with a named reviewer and the exact final file.
Field | What to record |
|---|---|
Source version | Approved script and capture revision |
Language and product scope | Locale, interface version and applicable plan or permissions |
Changed scenes | Scene IDs and reason for each edit |
Review evidence | Reviewer, date, final file and unresolved issues |
Publication destination | Help article, course lesson or video URL |
Release state | Needs revision, approved or published and checked |
Block publication when an instruction is wrong, a required condition is missing, or speech and captions refer to different versions. After replacing the video, play it from the actual help article or course page. Confirm the new file appears and the intended language is selected.
Frequently asked questions
Do I need to rerecord every language after a product update?
Review every affected language, then decide what to replace. Reusable visuals can remain when they still match the product. Whether audio can be regenerated in smaller sections depends on the tool and model; plan for a fresh export when necessary.
Can I fix the subtitles and keep the old dubbed audio?
Only if the spoken instruction is still accurate. If the narration names an obsolete button or omits a new prerequisite, changing subtitles leaves conflicting instructions in the video. Update both.
Does changing one language in Perso Dubbing update the others?
Do not assume it does. Review each existing language version separately, including its script and voice settings, before generating and approving the updated output.
Start with one tutorial affected by your latest release. Mark the changed scenes, approve the source, and use Perso Dubbing to prepare the language versions. Check the current plans and model options before generating. Record the final published URL beside each approved export.
Update multilingual tutorials by mapping the product change to each affected scene, then reviewing every published language version against the corrected source.
A button moves. A plan name changes. A setup flow gains a new step. Your English tutorial is easy to find, but its Spanish and Japanese versions may still teach the old workflow. Before generating another voice track, decide which parts of the lesson are still accurate.
Multilingual production already matters to paying users. In Perso Dubbing's paid cohort, 31.9% of 2,902 creators used two or more target languages between December 1, 2025 and August 31, 2026. This is usage on one platform, not a market estimate or evidence that multilingual publishing causes growth. Source: State of AI Dubbing 2026, Mid-Year Update.
The real example below comes from Perso Dubbing's November 2026 update to its product entry page. We compared the saved pre-change page with the current English, Korean and Spanish pages. The case shows how a new entry path changes what a tutorial must explain.
What needs to change in a multilingual tutorial?
Start with the instruction the viewer must follow. A correct translation can still direct someone to a button that no longer exists.
Product change | What to review | Likely action |
|---|---|---|
Color or spacing changes; the task is identical | Whether viewers can still identify the control | Keep the scene if it remains unambiguous; log the review |
A button or menu is renamed | Screen capture, narration, captions and each locale's actual UI label | Replace affected visuals and wording |
A step moves or a prerequisite is added | The complete task sequence and surrounding transitions | Record the revised task and review the full lesson |
A plan, permission or availability condition changes | Every scene and description stating the old condition | Correct the claim and verify the applicable audience |
Only a target-language translation is wrong | That language's script, audio and captions | Correct that version; check other versions for the same source ambiguity |
Keep a scene only when its instructions remain accurate for the product version your audience uses. If old and new interfaces coexist, label the tutorial's scope instead of silently replacing the only useful guide for an older version.
Build a change map before you dub again
Assign an ID to each task or scene. Connect it to the approved source script, visible UI labels and published language versions. Keep a copy of the previous source and exports so reviewers can see exactly what changed.
Verified example: the entry path now branches into desktop and online
Our saved pre-change page for Perso Dubbing's product home led with an online dubbing description and a free-trial action. By our November 11 check, the page presented a desktop download alongside a separate online action. The change was to the product entry guidance; this check does not establish when the desktop app itself first launched.
The current setup guidance adds requirements that an online-only tutorial cannot cover: a Perso account, a free API key when requested, a local voice model, and Hunyuan for local translation. It also distinguishes that translation route from ChatGPT, which uses the user's own account limits. Initial model downloads and computer-dependent processing are part of the setup.
We checked those setup conditions in the live English, Korean and Spanish page text. The English and Spanish entry controls were also checked in a browser. We did not install the app, generate a dub, or verify a finished localized tutorial.
For a tutorial starting on this page, the useful revision is a branch before the first click. An online lesson should identify the online action. A desktop lesson needs its own setup sequence. The following scene plan applies the verified change to an illustrative tutorial; it does not claim these video edits have already shipped.
Scene in the proposed revision | Keep or change | Evidence needed to approve it |
|---|---|---|
S01: choose the workflow | Replace the old entry capture; show which action the lesson follows | The displayed label and destination match the chosen route |
S02: prepare the desktop app | Add a desktop-only setup segment, including the account and model choices | A reviewer completes the shown setup on a supported computer; until then, mark the video segment unverified |
S03: upload and dub online | Retain only in the online branch after checking the current workspace | The recording still matches that workflow; desktop behavior is checked separately |
S04: explain the output | Review narration, captions and feature claims for the selected route | Every promise is supported for the demonstrated model and export |
The page change is verified. The scene plan is a recommended revision, with app execution still requiring its own check.
This distinction changes the release decision. A localized video can accurately translate the old narration and still omit a new setup requirement. Check the path the viewer must take before approving the wording.
Separate the scope of the edit from the scope of generation. A small script change does not guarantee that your selected dubbing tool or model can regenerate one sentence. If partial replacement is unavailable, generate a fresh version and assemble the approved material in your video editor.
Review the translated instruction against the screen
Give the language reviewer the new capture alongside the script. Ask them to follow the instruction as a viewer would.
If the product UI is localized, use the label shown in that locale. If the screen remains in English, preserve the English control label in the instruction and explain it in the viewer's language where needed. A dictionary translation of a button name can make the right control harder to find.
Maintain a small terminology table with the source label, each approved UI label, and any terms that must remain unchanged. Add version-specific names such as plan labels only after checking the current product.
With Perso Dubbing's video translation workflow, review the script and voice settings for each language before generating. Its product guidance explicitly warns against assuming that an edit in one language updates every existing version. Keep your release checklist outside that assumption.
For the initial production workflow, see our guide to localizing SaaS product demos. Use the update process here when the recorded product changes.
Check timing after the new wording is approved
Listen while watching the updated task. The instruction should arrive while the relevant control is visible, and the viewer should have time to recognize it before the next action.
If the translated line runs past the cut, first remove unnecessary wording without losing conditions. If it still needs more time, extend the screen hold or revise the edit. Speeding up the voice can make a setup tutorial harder to follow.
Check the boundary before and after the replacement: audio level, voice continuity, pauses and subtitle timing. Our product demo timing guide covers the initial synchronization problem; these same checks apply again after an update.
Keep a release record for every language
A finished source video does not establish that every localized export is ready. Use one row per destination language, with a named reviewer and the exact final file.
Field | What to record |
|---|---|
Source version | Approved script and capture revision |
Language and product scope | Locale, interface version and applicable plan or permissions |
Changed scenes | Scene IDs and reason for each edit |
Review evidence | Reviewer, date, final file and unresolved issues |
Publication destination | Help article, course lesson or video URL |
Release state | Needs revision, approved or published and checked |
Block publication when an instruction is wrong, a required condition is missing, or speech and captions refer to different versions. After replacing the video, play it from the actual help article or course page. Confirm the new file appears and the intended language is selected.
Frequently asked questions
Do I need to rerecord every language after a product update?
Review every affected language, then decide what to replace. Reusable visuals can remain when they still match the product. Whether audio can be regenerated in smaller sections depends on the tool and model; plan for a fresh export when necessary.
Can I fix the subtitles and keep the old dubbed audio?
Only if the spoken instruction is still accurate. If the narration names an obsolete button or omits a new prerequisite, changing subtitles leaves conflicting instructions in the video. Update both.
Does changing one language in Perso Dubbing update the others?
Do not assume it does. Review each existing language version separately, including its script and voice settings, before generating and approving the updated output.
Start with one tutorial affected by your latest release. Mark the changed scenes, approve the source, and use Perso Dubbing to prepare the language versions. Check the current plans and model options before generating. Record the final published URL beside each approved export.
Update multilingual tutorials by mapping the product change to each affected scene, then reviewing every published language version against the corrected source.
A button moves. A plan name changes. A setup flow gains a new step. Your English tutorial is easy to find, but its Spanish and Japanese versions may still teach the old workflow. Before generating another voice track, decide which parts of the lesson are still accurate.
Multilingual production already matters to paying users. In Perso Dubbing's paid cohort, 31.9% of 2,902 creators used two or more target languages between December 1, 2025 and August 31, 2026. This is usage on one platform, not a market estimate or evidence that multilingual publishing causes growth. Source: State of AI Dubbing 2026, Mid-Year Update.
The real example below comes from Perso Dubbing's November 2026 update to its product entry page. We compared the saved pre-change page with the current English, Korean and Spanish pages. The case shows how a new entry path changes what a tutorial must explain.
What needs to change in a multilingual tutorial?
Start with the instruction the viewer must follow. A correct translation can still direct someone to a button that no longer exists.
Product change | What to review | Likely action |
|---|---|---|
Color or spacing changes; the task is identical | Whether viewers can still identify the control | Keep the scene if it remains unambiguous; log the review |
A button or menu is renamed | Screen capture, narration, captions and each locale's actual UI label | Replace affected visuals and wording |
A step moves or a prerequisite is added | The complete task sequence and surrounding transitions | Record the revised task and review the full lesson |
A plan, permission or availability condition changes | Every scene and description stating the old condition | Correct the claim and verify the applicable audience |
Only a target-language translation is wrong | That language's script, audio and captions | Correct that version; check other versions for the same source ambiguity |
Keep a scene only when its instructions remain accurate for the product version your audience uses. If old and new interfaces coexist, label the tutorial's scope instead of silently replacing the only useful guide for an older version.
Build a change map before you dub again
Assign an ID to each task or scene. Connect it to the approved source script, visible UI labels and published language versions. Keep a copy of the previous source and exports so reviewers can see exactly what changed.
Verified example: the entry path now branches into desktop and online
Our saved pre-change page for Perso Dubbing's product home led with an online dubbing description and a free-trial action. By our November 11 check, the page presented a desktop download alongside a separate online action. The change was to the product entry guidance; this check does not establish when the desktop app itself first launched.
The current setup guidance adds requirements that an online-only tutorial cannot cover: a Perso account, a free API key when requested, a local voice model, and Hunyuan for local translation. It also distinguishes that translation route from ChatGPT, which uses the user's own account limits. Initial model downloads and computer-dependent processing are part of the setup.
We checked those setup conditions in the live English, Korean and Spanish page text. The English and Spanish entry controls were also checked in a browser. We did not install the app, generate a dub, or verify a finished localized tutorial.
For a tutorial starting on this page, the useful revision is a branch before the first click. An online lesson should identify the online action. A desktop lesson needs its own setup sequence. The following scene plan applies the verified change to an illustrative tutorial; it does not claim these video edits have already shipped.
Scene in the proposed revision | Keep or change | Evidence needed to approve it |
|---|---|---|
S01: choose the workflow | Replace the old entry capture; show which action the lesson follows | The displayed label and destination match the chosen route |
S02: prepare the desktop app | Add a desktop-only setup segment, including the account and model choices | A reviewer completes the shown setup on a supported computer; until then, mark the video segment unverified |
S03: upload and dub online | Retain only in the online branch after checking the current workspace | The recording still matches that workflow; desktop behavior is checked separately |
S04: explain the output | Review narration, captions and feature claims for the selected route | Every promise is supported for the demonstrated model and export |
The page change is verified. The scene plan is a recommended revision, with app execution still requiring its own check.
This distinction changes the release decision. A localized video can accurately translate the old narration and still omit a new setup requirement. Check the path the viewer must take before approving the wording.
Separate the scope of the edit from the scope of generation. A small script change does not guarantee that your selected dubbing tool or model can regenerate one sentence. If partial replacement is unavailable, generate a fresh version and assemble the approved material in your video editor.
Review the translated instruction against the screen
Give the language reviewer the new capture alongside the script. Ask them to follow the instruction as a viewer would.
If the product UI is localized, use the label shown in that locale. If the screen remains in English, preserve the English control label in the instruction and explain it in the viewer's language where needed. A dictionary translation of a button name can make the right control harder to find.
Maintain a small terminology table with the source label, each approved UI label, and any terms that must remain unchanged. Add version-specific names such as plan labels only after checking the current product.
With Perso Dubbing's video translation workflow, review the script and voice settings for each language before generating. Its product guidance explicitly warns against assuming that an edit in one language updates every existing version. Keep your release checklist outside that assumption.
For the initial production workflow, see our guide to localizing SaaS product demos. Use the update process here when the recorded product changes.
Check timing after the new wording is approved
Listen while watching the updated task. The instruction should arrive while the relevant control is visible, and the viewer should have time to recognize it before the next action.
If the translated line runs past the cut, first remove unnecessary wording without losing conditions. If it still needs more time, extend the screen hold or revise the edit. Speeding up the voice can make a setup tutorial harder to follow.
Check the boundary before and after the replacement: audio level, voice continuity, pauses and subtitle timing. Our product demo timing guide covers the initial synchronization problem; these same checks apply again after an update.
Keep a release record for every language
A finished source video does not establish that every localized export is ready. Use one row per destination language, with a named reviewer and the exact final file.
Field | What to record |
|---|---|
Source version | Approved script and capture revision |
Language and product scope | Locale, interface version and applicable plan or permissions |
Changed scenes | Scene IDs and reason for each edit |
Review evidence | Reviewer, date, final file and unresolved issues |
Publication destination | Help article, course lesson or video URL |
Release state | Needs revision, approved or published and checked |
Block publication when an instruction is wrong, a required condition is missing, or speech and captions refer to different versions. After replacing the video, play it from the actual help article or course page. Confirm the new file appears and the intended language is selected.
Frequently asked questions
Do I need to rerecord every language after a product update?
Review every affected language, then decide what to replace. Reusable visuals can remain when they still match the product. Whether audio can be regenerated in smaller sections depends on the tool and model; plan for a fresh export when necessary.
Can I fix the subtitles and keep the old dubbed audio?
Only if the spoken instruction is still accurate. If the narration names an obsolete button or omits a new prerequisite, changing subtitles leaves conflicting instructions in the video. Update both.
Does changing one language in Perso Dubbing update the others?
Do not assume it does. Review each existing language version separately, including its script and voice settings, before generating and approving the updated output.
Start with one tutorial affected by your latest release. Mark the changed scenes, approve the source, and use Perso Dubbing to prepare the language versions. Check the current plans and model options before generating. Record the final published URL beside each approved export.
Continue Reading
Browse All
