Software UI Japanese: Buttons, Error Messages, and Confirmation Language

Core examples: 保存, 送信, 削除, 確定, キャンセル, 戻る, 再試行, エラー, 読み込み中, 本当に削除しますか.

Tiny text can cause big actions

A button says:

確定

Another says:

削除

A dialog asks:

本当に削除しますか。

Software UI Japanese is short because space is limited. But short UI strings can save data, send forms, delete accounts, authorize payment, or cancel workflows.

The key principle is:

UI Japanese must be read by action type and reversibility.

Before clicking, classify the string: status, navigation, draft action, final action, warning, error, or recovery.

保存

保存

means save.

Related:

下書き保存 save draft

自動保存 autosave

保存しました saved

保存できませんでした could not save

保存 usually keeps data, but location and visibility matter. Saving a draft is not the same as publishing or sending.

Learner action: check whether 保存 is local, draft, cloud, public, or final.

送信

送信

means send/submit.

Related:

送信する send

送信完了 sent/submission complete

送信できませんでした could not send

フォームを送信 submit form

送信 is more final than 保存 in many contexts. It may send data to another person, server, company, or authority.

Learner action: do not press 送信 if you only meant to save.

削除

削除

means delete.

Related:

完全に削除 delete permanently

ゴミ箱に移動 move to trash

復元 restore

取り消し undo/cancel

Deletion may be reversible or irreversible. The UI must tell you.

確定

確定

means finalize/confirm/settle.

This is a high-attention button.

Examples:

注文を確定 finalize order

内容を確定 finalize contents

予約を確定 confirm reservation

確定 usually means the choice becomes fixed or submitted. It may be final.

Learner action: treat 確定 as stronger than 確認.

確認

確認

means confirm/check/review.

It may label a review step:

入力内容の確認 review entered information

The next screen may have 確定 or 送信.

Learner action: 確認 is often not final, but it may lead to a final action.

キャンセル and 戻る

キャンセル

means cancel.

戻る

means go back.

These are different. 戻る usually returns to previous screen. キャンセル may cancel the workflow, reservation, or action.

Learner action: if an action is already confirmed, キャンセル may not mean undo is available.

再試行

再試行

means retry.

Related:

もう一度お試しください please try again

通信環境をご確認ください check your connection

時間をおいて再度お試しください wait and try again later

再試行 belongs to recovery after failure.

エラー and status messages

エラー

means error.

Common status labels:

読み込み中 loading

処理中 processing

完了 complete

失敗 failed

無効 invalid

必須項目 required field

Learner action: identify whether the screen is waiting, failed, complete, or asking for correction.

Confirmation dialogs

High-attention confirmation phrases:

本当に削除しますか。 Are you sure you want to delete?

この操作は取り消せません。 This operation cannot be undone.

よろしいですか。 Is this okay? / Do you want to proceed?

上書きしますか。 Overwrite?

変更を保存せずに終了しますか。 Exit without saving changes?

Confirmation Japanese often uses polite softness while asking about irreversible action.

Error cause and recovery

Error messages may contain:

入力内容に誤りがあります。 There is an error in the entered information.

必須項目を入力してください。 Please enter required fields.

認証に失敗しました。 Authentication failed.

権限がありません。 You do not have permission.

サーバーに接続できません。 Cannot connect to server.

Learner action: find whether the fix is input correction, login, permission, network, retry, or contact support.

Example bank walkthrough

保存

Save.

Learner action: keep data, not necessarily send.

送信

Send/submit.

Learner action: transmits data.

削除

Delete.

Learner action: check reversibility.

確定

Finalize/confirm.

Learner action: often final action.

キャンセル

Cancel.

Learner action: may cancel workflow/action.

戻る

Go back.

Learner action: navigation.

再試行

Retry.

Learner action: attempt again after failure.

エラー

Error.

Learner action: identify cause.

読み込み中

Loading.

Learner action: wait.

本当に削除しますか

Are you sure you want to delete?

Learner action: deletion confirmation.

UI string checklist

For any UI Japanese string:

1. Type: status, navigation, action, warning, error, confirmation, help?
2. Object: what will be saved/sent/deleted/finalized?
3. Direction: local, server, other user, public?
4. Finality: reversible or not?
5. Cost/risk: payment, deletion, privacy, publication?
6. Error cause: input, network, permission, authentication?
7. Recovery: retry, correct, cancel, contact support?
8. Next button: 確認, 確定, 送信, 削除?

UI action-finality table

Software UI Japanese is short, so classify before clicking.

Never treat 確定 as a decorative “OK.” It often finalizes.

Error-message parse

A useful error-message routine:

1. What failed?
2. Why did it fail?
3. Is user input wrong?
4. Is network/server unavailable?
5. Can the action be retried?
6. Was any data saved or sent?
7. Is there a contact/support code?

Common phrases:

入力内容に誤りがあります there is an error in entered information

通信エラーが発生しました communication error occurred

時間をおいて再度お試しください try again later

Destructive-action warning

Before clicking 削除, 初期化, 退会, 解約, or リセット, look for:

元に戻せません cannot be undone

すべて削除されます all will be deleted

復元できません cannot be restored

These are the UI equivalents of red flags.

A strong tool for this article would label UI strings by action and reversibility.

Suggested functions:

1. Button risk labels: save, submit, delete, finalize.
2. Confirmation-dialog parser.
3. Error-cause classifier.
4. Reversibility warning.
5. Required-field detector.
6. Recovery path suggestion.
7. Before-click checklist.

Final rule

Software UI Japanese is action language under space pressure.

保存 keeps. 送信 submits. 削除 removes. 確定 finalizes. キャンセル cancels. 戻る navigates. 再試行 retries. エラー explains failure.

Before clicking, ask: what happens, to what, and can I undo it?