Clockify limits

How to export Clockify reports longer than 31 days

If Clockify's report date picker refused a twelve-month range, you are not doing it wrong. The Free-plan limit is real. Here are four ways to get a full year of time entries, including a Google Sheets option that avoids repeated manual exports.

The cap

Where the 31-day cap actually appears

Clockify's help centre lists it among the Free plan restrictions as “Report and dashboard date range filter: 1 month (31 days) at a time”. Note what that covers: the filter, not one report type. Detailed, Summary and Weekly are not carved out separately, and the dashboard sits under the same cap.

Clockify's own pages word it differently, which is why search results contradict each other: the export help page says “a maximum of 31 days or 1 month per report”, while the Free plan features overview says “a maximum date range of 1 month” and never mentions 31 days.

The export is capped twice over

Even inside a legal window, Free exports PDF only: “PDF (Free plan) or CSV/Excel (Basic plan or higher)”, and “A PDF file can contain up to 3000 rows.” You get a document, not data — and the document has its own ceiling.

The API is a separate question

Clockify's article on exporting via the API points at POST /v1/workspaces/{workspaceId}/reports/detailed and the matching /reports/summary, and its example request uses a full calendar year. That page documents no 31-day restriction there.

Route one

The manual method: twelve monthly PDF exports

Clockify's own suggestion is to run and export month by month: calendar months are all 31 days or fewer, so twelve of them clear the filter.

Set the range, run the Detailed report, export, rename the download, repeat eleven times — at three optimistic minutes a slice, most of an hour. Then it stops being useful, because you cannot sum a PDF or point an invoice formula at it — you retype or convert and clean the columns twelve times, against a 3,000-row ceiling per file.

Route two

The API method: loop month by month, append into one sheet

The Clockify API works on Free: access was rate-limited in April 2026, not removed.

1. Loop the reports endpoint

   Twelve POST calls to /v1/workspaces/{workspaceId}/reports/detailed, each with dateRangeStart and dateRangeEnd one month apart, appending as you go. Clockify documents JSON, CSV, XLSX and PDF as export values there, but repeats that CSV/Excel is Basic or higher — on Free, take JSON.

2. Or page the time-entries endpoint

   GET /v1/workspaces/{workspaceId}/user/{userId}/time-entries returns your own entries page by page — a different endpoint from the reports one.

3. Set page-size, or pay for it later

   Clockify returns 50 results per page by default; the documented maximum is “max 5000 for base and 1000 for report endpoints”. Leaving the default is the commonest way to turn a backfill into a rate-limit failure.

Afterwards

Keeping the sheet current instead of re-exporting every quarter

The backfill is a one-off; the recurring cost is next quarter. The cheaper shape is a sheet that is the record, refreshed in place: a top-up needs only the days since the last run — inside 31 days, so the cap stops applying and the request count drops to a handful.

This add-on

How HourSync handles a multi-month backfill

HourSync is a Google Sheets add-on that imports Clockify time entries into your spreadsheet. On a long backfill, read off its source:

• The sidebar asks “Import the last N days”: a number field, minimum 1, maximum 3,650. A year is 365.
• It does not call the reports endpoints. It calls GET /workspaces/{id}/user/{userId}/time-entries with page-size=200, page by page, and sends no date parameters. The cutoff — now minus N days — is applied in Apps Script as rows are read.
• Every import rewrites the Hours sheet in place, so re-running a backfill cannot leave duplicate rows behind.

The honest consequence: since no date filter reaches Clockify, the number of API calls scales with the size of your history, not with the window you asked for. On a Free workspace with a long history and 30 requests an hour, a large backfill can hit the limit. HourSync retries with exponential backoff over four attempts — enough for a momentary throttle, not a per-hour quota — then stops and says so rather than leaving a truncated sheet. Wait out the hour and re-run.