Freelance Billing Live Timer
Track exact freelance time and live value, then apply minimum time and increment rounding to estimate a billable amount.
Last updated: August 2026
Enter your hourly billing rate and start the timer.
Current billable amount
Estimated billable amount based on the rate, included time, and billing rules entered. This is not an official invoice or contract interpretation.
How does the freelance billing timer work?
Raw value equals hourly billing rate multiplied by exact included hours. For positive time, the calculator applies the minimum first, then the selected increment and rounding method. Final billable amount equals hourly rate multiplied by final billable hours.
What is a billing increment?
An increment converts exact elapsed time into units such as 6, 10, 15, or 30 minutes. For example, 17 minutes rounded up to 15-minute increments becomes 30 billable minutes. Your agreement determines the applicable rule.
Why are live value and billable amount different?
The continuously moving value uses exact included time. The billable amount applies the entered minimum and rounding rules. With exact time and no minimum, they match before display rounding.
How does minimum billable time work?
Once positive work time exists, the duration is raised to the minimum before increment rounding. At exactly zero elapsed time, no minimum is applied.
Frequently asked questions
What is a 6-minute increment?
Six minutes equals 0.1 hour, so one hour contains ten units.
How are 17 minutes billed in 15-minute increments?
Round up produces 30 minutes; nearest or down produces 15 minutes.
Can I pause non-billable time?
Yes. Paused time is excluded from both exact and billable duration.
Can I enter work already started?
Yes. Enter its local start time and any excluded minutes already taken.
Does this create an invoice?
No. It provides an estimate and copyable summary, not an official invoice.
Privacy and local history
Calculations remain in the browser and values are not persisted or sent to analytics. Local history and CSV export were intentionally omitted to keep this release stateless and avoid introducing a rushed persistence layer.