← Finance

Mortgage Rate Increase Simulator

Compare monthly payment and total-interest impact when mortgage rates rise over time.

Other languages 日本語 | English | Español | Français

Inputs

Rate-change schedule

Initial rate at year 0 is auto-applied. Enter only change points here.

Years from start New annual rate (%) Action
Advanced settings

This version fixes calculation mode to reamortize at each rate-change point.

Comparison summary

Trend chart

Yearly comparison

Notes

FAQ

How is payment recalculated after a rate change?

At each rate-change point, payment is recalculated from the remaining balance and remaining term (reamortization model).

What does baseline comparison mean?

Baseline assumes the initial rate remains constant for the full term. Scenario results show how much total interest, total paid, and maximum payment increase.

Does this match every lender contract rule?

No. Lender-specific caps, reset windows, and payment limits vary. Use this as a comparison model, then verify contract details.

Can I use this before checking refinance options?

Yes. First estimate stress under higher rates, then compare refinance cost-recovery with a refinance break-even calculator.

What should I do first on this page?

Start with the minimum required inputs or the first action shown near the primary button. Keep optional settings at defaults for a baseline run, then change one setting at a time so you can explain what caused each output change.

How to use Mortgage Rate Increase Simulator effectively

What this calculator does

This page is for estimating outcomes by changing inputs in one controlled workflow. The model keeps your focus on variables, not output shape. Start with stable assumptions, then test sensitivity by changing one key input at a time to observe directional impact.

Input meaning and unit policy

Each input has an expected unit and a typical range. For reliable interpretation, check whether you are using the same unit system, period, and base assumptions across all runs. Unit mismatch is the most common source of unexpected drift in numeric results.

Use-case sequence

A practical sequence is: first run with defaults, then create a baseline log, then run one alternative scenario, and finally compare only the changed output metric. This sequence reduces cognitive load and prevents false pattern recognition in early experiments.

Common mistakes to avoid

Avoid changing too many variables at once, mixing incompatible data sources, and interpreting a one-time output without checking robustness. A single contradictory input can flip conclusions, so keep each experiment minimal and document assumptions as part of your note.

Interpretation guidance

Review both magnitude and direction. Direction tells you whether a strategy moves outcomes in the desired direction, while magnitude helps you judge practicality. If both agree, you can proceed; if not, rebuild the baseline and verify constraints before deciding.