Relativistic Commute Planner
Plan a commute when clocks do not agree
A normal commute planner tells you how long the trip takes on one shared clock. A relativistic commute planner has to do something stranger: it has to track the time measured by observers who stay in the Earth frame and the time experienced by the traveler riding in the ship. If the ship moves at only a small fraction of the speed of light, those two answers are nearly the same. Once the cruise speed climbs toward light speed, they separate dramatically. This calculator is for that split. It lets you enter a one-way distance in light-years, a cruise speed as a percentage of light speed, and the number of days you remain at the destination before returning. The result is a pair of timelines you can compare directly.
That distinction matters because the question is not simply how long the route feels. A futuristic worker commuting to a remote station may care about at least two clocks at once: the schedule followed by colleagues and family who remain on Earth, and the aging experienced on the journey. Earth may wait years for a round trip that feels significantly shorter to the traveler. In other words, the commute is not just a travel problem. It is a planning problem about deadlines, coordination, and the gap between calendar time and proper time.
This page keeps the model deliberately simple. It does not try to solve propulsion, acceleration comfort, or orbital insertion. Instead, it answers a clear scheduling question: given a fixed distance, a constant cruise speed below the speed of light, and a stay at the destination, how many days pass on Earth and how many days pass for the traveler over the full out-and-back commute?
What each input means in plain language
One-way distance (light years) is the distance from Earth to the workplace for a single leg of the trip. If the destination is 4 light-years away, enter 4, not 8. The calculator handles the round trip internally by doubling the travel time. This is an Earth-frame distance, which is the usual way the route is described in astronomy and in introductory relativity examples.
Cruise speed (% of light speed) is the ship's constant coasting speed expressed as a percentage of c, the speed of light. Enter 80 for eighty percent of light speed, 95 for ninety-five percent, and so on. The value must stay below 100, because special relativity does not allow a massive object to reach or exceed light speed. The speed input has the biggest effect on time dilation. Moving from 50% of light speed to 60% changes the result, but moving from 95% to 99% changes it even more sharply because the relativistic factor rises nonlinearly near c.
Days spent at destination is the layover or work period between the outbound and return legs. In this simplified planner, that stay is added equally to both totals. If you remain parked relative to the destination for 10 days, the calculator adds 10 days to the Earth-frame total and 10 days to the traveler's total. That means the dramatic difference between the two outputs comes entirely from the high-speed travel segments, not from the time spent resting or working after arrival.
A good habit is to think through the units before you calculate. Distance here is in light-years, speed is a percent of light speed, and the result is presented in days. If your source distance is in astronomical units or parsecs, convert before entering it. If you are sketching several possible commutes, keep the stay fixed and vary only one other input at a time. That makes the effect of speed or distance easier to see.
How the calculator does the physics
The JavaScript on this page uses a compact special-relativity model. First it converts the speed percentage into a fraction of light speed. If you enter 80, the code uses v = 0.80. Because one light-year traveled at light speed takes one year, the Earth-frame one-way travel time in years is simply distance divided by that fraction. The script then converts years into days by multiplying by 365.25.
Next comes the relativity step. The Lorentz factor, usually written as gamma, tells you how strongly moving clocks differ from stationary ones. As speed approaches light speed, gamma grows quickly.
The traveler experiences less time during each cruise segment, so the one-way proper time is the Earth-frame one-way travel time divided by gamma.
Finally, the page doubles the outbound travel for the return leg and adds the destination stay to both clocks.
If you like abstract notation, you can also view the planner as a function that maps a few inputs to a pair of outputs. The page originally expressed that general idea with the MathML below, and it still applies here: Earth time and traveler time are both functions of distance, speed, and stay duration.
Worked example
Suppose your workplace is 4 light-years away, your ship cruises at 80% of light speed, and you spend 30 days there before coming home. The speed fraction is 0.80, so the Earth-frame one-way travel time is 4 ÷ 0.80 = 5 years. Converting to days gives 5 × 365.25 = 1826.25 days for the outbound leg as measured by Earth-bound observers.
At 80% of light speed, gamma is about 1.6667. Divide the Earth-frame one-way travel time by gamma and the traveler experiences about 1095.75 days for that same one-way leg. Doubling for the return trip gives 3652.5 days on Earth and 2191.5 days for the traveler while in transit. Then add the 30-day stay to both totals.
The final result is an Earth-frame duration of 3682.5 days and a traveler duration of 2221.5 days. Those numbers are both long, but they are not close. Earth has aged about 1461 days more than the commuter by the time the traveler returns. That is the practical meaning of time dilation in this planner: two reasonable clocks, both correct in their own frame, produce different totals for the same commute scenario.
Notice what the example teaches. Doubling the distance would double both travel totals. Increasing the stay would add the same amount to both totals and would not change the amount of dilation accumulated in transit. Raising the cruise speed would reduce both totals, but it would shrink the traveler's total faster once the speed is already very high. That last point is the one people most often underestimate when they first play with relativistic schedules.
How to read the result panel
When you press the button, the result panel reports two numbers in days. Earth-frame duration is the total elapsed time for observers who remain in the rest frame used by the planner. Traveler duration is the total proper time experienced by the commuter over the same round trip and stay. The smaller of the two is normally the traveler duration, because the ship spends its travel segments moving at relativistic speed.
If you want a quick measure of the age gap created by the commute, subtract the traveler duration from the Earth-frame duration. This page does not display that subtraction separately, but it is easy to interpret from the two reported values. A tiny gap means the speed is not high enough for dramatic dilation. A large gap means coordination with Earth calendars, meetings, and long-term planning becomes much harder, even if the traveler personally experiences a shorter trip.
One good sanity check is to imagine the speed getting slower. As the cruise speed drops, both totals should rise, and the difference between them should usually shrink. Another check is to imagine the speed moving closer to 100% of light speed while staying below it. Earth time will still remain substantial because the destination is still far away, but traveler time will compress more strongly because gamma keeps growing.
Scenario intuition table
The table below holds distance and stay fixed at 2 light-years one way and 14 days at the destination, then changes only cruise speed. The pattern is more important than the exact decimals: faster cruising shortens the commute for everyone, but the traveler's own clock pulls away from Earth more dramatically at the highest speeds.
| Cruise speed | Earth-frame total | Traveler total | What it means |
|---|---|---|---|
| 50% of light speed | 2936.0 days | 2544.9 days | Long trip, modest but noticeable dilation. |
| 80% of light speed | 1840.3 days | 1109.8 days | Transit shortens sharply, and the traveler's clock falls far behind Earth. |
| 95% of light speed | 1551.9 days | 494.2 days | Earth still waits years, while the traveler experiences well under a year and a half. |
This is why relativistic travel planning is counterintuitive. The Earth total does not vanish just because the ship is extremely fast; distance still matters. What changes most strongly is the relation between the two clocks. Near light speed, small increases in speed can produce large changes in experienced time on board.
Assumptions, limits, and edge cases
This calculator is intentionally a clean special-relativity estimator, not a mission simulator. It assumes the ship instantly reaches the chosen cruise speed, instantly turns around, and cruises at the same speed on the way back. Real missions would include acceleration periods, fuel constraints, route geometry, communication lag, and probably gravity from stars or stations. None of those are modeled here, so use the result as a schedule estimate rather than an engineering design.
The page also treats the destination stay as a plain number of days added equally to both clocks. That is a reasonable simplification for a quick planner, but it means the stay itself is not modeled as occurring in a different gravitational environment or in a separate moving frame. The strongest relativistic effect in this tool therefore comes from the cruise segments alone.
Finally, remember that the speed field is highly sensitive near 100. Entering 99 instead of 90 is not a small tweak in this context. If you are testing a scenario that feels extreme, run a few nearby values as a comparison set. That makes the nonlinear behavior obvious and helps you avoid treating one dramatic output as the only plausible answer. A calculator like this is most useful when it supports comparison, not when it is used as a single mysterious oracle.
Optional mini-game: Gamma Window Dispatch
This arcade-style mini-game uses the same idea as the calculator above, but turns it into a fast tuning challenge. Each mission generates a commute with a distance and a stay. Your job is to drag the throttle to a cruise speed that places both the Earth-time marker and the traveler-time marker inside their glowing target windows, then launch before the mission timer expires. It is a quick way to build intuition for how nonlinear the speed input becomes near light speed.
Best score on this device: 0. Every mission reuses the same distance, speed, gamma, and proper-time relationships explained in the calculator section.