A Fiverr level is a platform status based on specified metrics and evaluation rules. It is not a guarantee of orders or evidence that a seller fits every project. Use the official criteria and your own Level Overview together, then investigate the service habits you can actually observe.
Current published thresholds
Snapshot checked 23 October 2026 against Fiverr's freelancer-level page. Verify the page again before making an account decision.
| Metric | Level 1 | Level 2 | Top Rated |
|---|---|---|---|
| Success Score | 5+ | 7+ | 9+ |
| Rating | 4.4+ | 4.6+ | 4.7+ |
| Response rate | 80% | 90% | 90% |
| Completed orders | 5 | 20 | 40 |
| Unique clients | 3 | 10 | 20 |
| Earnings | USD 400 | USD 2,000 | USD 10,000 |
| Additional evaluation | No | No | Yes |
The guidance says all six metrics must qualify for Level 1 or Level 2; Top Rated also requires manual evaluation. Meeting only an order or earnings threshold is not enough. Pro status is a separate programme and can coexist with a seller level.
Read each measure as its own measure
Orders and unique clients answer different questions: repeated orders from one buyer increase one count without adding another unique buyer. Response rate concerns replies to new messages within the stated period; it is not the same as average response time. Copy the exact metric name and evaluation period from your account rather than mixing numbers from different screens.
Success Score is not a number this site can reverse-engineer from one late delivery or one review. A score change and a particular incident occurring together do not establish that incident as the sole cause.
A worked dashboard diagnosis
Imagine a seller has 20 orders, 10 unique clients and USD 2,000 earnings, but a Success Score of 6. Under the published snapshot, the order, client and earnings figures match Level 2, but the score is below 7. The appropriate conclusion is “one displayed requirement is not met,” not “the system forgot to promote me.” Other metrics still need checking too.
Download the seller-level review sheet. For each metric, enter the dashboard value, period, relevant criterion and source date. Keep evidence and possible explanations in separate columns.
Investigate service problems without manufacturing metrics
| Observation | Records to inspect | Practical response |
|---|---|---|
| Repeated unclear feedback | Original requirements and revision messages | Add a focused approval question |
| Delivery dates repeatedly at risk | Time estimates and input arrival dates | Narrow scope or allow more time |
| Missed new enquiries | Actual availability and message history | Set a realistic response routine |
| Frequent scope disputes | Listing and accepted order details | Clarify included units and exclusions |
These actions improve a service process. They are not a disclosed formula for increasing Success Score. Never buy orders, exchange reviews or pressure a buyer to influence a level.
Check a warning directly
The official page describes a grace period when performance falls below a current level, and different account states for policy-related issues. Follow the actual notice and deadline in your account. Do not assume that every lower number means an account restriction or that posting more Gigs resolves a policy issue.
Use the delivery checklist to reduce omissions and the scope worksheet to make the offer understandable. Keep the focus on the work and the evidence behind it.
Official references
Source pages checked on 23 October 2026. These references support platform facts; the practice scenarios and worksheets are our educational examples. Confirm account-specific conditions with the provider.
Practice work and illustrative amounts are labelled in the article. See how we prepare and correct guides and how the resource checks work. Report a specific error or broken step.