Fortnite Chest Tracker

Keep a session history, not just a running number. Log each run by date and chest type, then see how far your recorded openings take you toward your own target.

How to use the Fortnite chest tracker for a session

Use this Fortnite chest tracker after a match or a clearly defined group of matches. It records how many chests you entered for that period, split into normal, rare and other/event categories. Each saved entry has a date and an optional note. The progress bar compares the sum of your entries with a goal you choose; it is not connected to a Fortnite quest or reward system.

Decide where a session begins and ends before entering numbers. One match per entry is easy to review. One evening per entry is also workable if you consistently group those matches. Avoid mixing an evening total with separate entries for matches already included in that evening. The tool can validate numbers, but it cannot recognize that two differently named records describe the same openings.

A session template you can copy

Session date: use the date you played, not necessarily the date you type the entry. The form starts with today’s local date. If a run crossed midnight, choose one consistent convention, such as the date it began, and mention that convention in the note when it matters. A date identifies the period; it does not establish a connection to game servers.

Normal chests: enter the ordinary chest openings you chose to track during that session. Rare chests: enter your separately observed rare openings. Other / event chests: reserve this for another category you deliberately want to distinguish. Each category accepts a whole number from zero to 10,000. Zero means you recorded none in that category. At least one category must have a positive count before a session can be saved.

Note: describe the context in up to 120 characters. Useful details include the mode, route, objective wording, whether the record is partial, or a boosted event period. “Two matches, normal rate, own openings only” is easier to interpret later than “good run.” Avoid storing account credentials or private room codes in notes you may export and share.

An example entry with 18 normal chests, three rare chests and two other chests totals 23. If those categories describe overlapping observations, correct the categorization before saving: a rare chest entered under both normal and rare would be counted twice. Categories are organizational labels, not certification that an opening qualifies for a particular Epic reward.

Choose between the live counter and the session log

The homepage Fortnite chest counter is for tapping during play. It provides quick additions, subtraction, undo and shared squad rooms. This page is for reviewing completed runs by date and category. The two records are independent: saving 23 here does not add 23 to the homepage, and a tap on the homepage does not create a dated session here.

If your live counter starts at 400 and ends at 423, the session contains 23 new openings. Enter 23 across the appropriate categories. Do not enter 423 unless this session really covers all 423 openings. The difference between a cumulative checkpoint and a session increment is the most common source of inflated manual histories.

If your starting number came from a quest, use the guide to checking chests opened in Fortnite to establish its scope first. A quest tally might describe a specific objective rather than everything you opened. You can retain that checkpoint in a note without importing it into every session. This lets the log describe your own recorded activity consistently.

Set a useful chest goal

Choose a goal for the activity you are recording, such as 100 openings across several sessions. The goal is a positive whole number and can be changed independently of the history. Changing it does not add or remove chests. The percentage uses all saved sessions in this browser, so it is a cumulative log goal rather than a separate target for each row.

For example, 23 recorded openings against a goal of 100 displays 23%. After another session of 17, the total becomes 40 and the progress becomes 40%. If you reduce the goal to 20, the displayed bar stops at 100%, while the logged total still reads 40. Reaching the target does not unlock a reward or tell you that a Pirate Token is due.

Pick a goal that helps you organize your play, and stop when you choose. A progress bar is not a reason to keep playing. To understand how a count relates to a stated drop rate, use the separate Pirate Token probability calculator. Its result is a probability under assumptions, not a completion percentage for a guaranteed prize.

Read and check the exported JSON

Select Export session history to download lootcounter-sessions.json. The file contains a format version, your goal and a list of sessions. Each session includes an ID, date, the three category counts and its note. These are your manual records. The file does not contain verified Epic match data, an account connection or proof of ownership of any reward.

Open the file in a text editor to review it. A session with normal: 18, rare: 3 and event: 2 represents 23 openings. Add those three fields for each entry, then add the entry totals to reproduce the logged total. The goal field is the target; it must not be added to the chest counts. The session ID distinguishes records and is not a reward code.

Save exports with a descriptive filename if you keep several backups, for example a date followed by “evening-sessions.” Renaming a downloaded file does not update the in-browser log. This version provides export only: there is no import button, automatic restore or cloud synchronization. A readable export remains useful for review even when you cannot load it back into this interface.

Record a squad run without counting it twice

For live cooperation, create or join a room on the homepage. Each player records their own openings there, and the room shows the sum of active members. After the run, each person can save their own contribution in this session tracker. Four players with 18, 23, 11 and eight openings have a combined run of 60, but the player who opened 18 should save 18 in their personal log.

If one organizer instead keeps a separate team log, label that scope explicitly and use it consistently. Do not combine a team-total entry with the individual entries that make it up. Room totals can also change when a member is removed, so a room’s later active total may differ from the numbers you recorded at the end of the run.

Correct mistakes and protect local history

Review the date, categories and note before saving. There is no edit-in-place control in this version. If an entry is wrong, keep a note of the correct values, remove the incorrect entry through its confirmation dialog, and add the corrected one. Removing an entry changes the total and progress immediately. Export first if you want a record of the original history.

Up to 500 sessions can be stored in this log. At the limit, export your history and decide which entries to retain before adding another. Keep edits in one tab at a time because simultaneous tabs can overwrite each other’s local changes. The log belongs to this browser profile, not an Epic login, so another device will have a separate history.

If browser storage cannot be written, the page shows a warning. Export the current data before closing the page. If existing saved data has an invalid format, the tracker preserves it and offers an original-data download rather than silently replacing it with an empty log. Do not assume a refresh will repair a damaged record. The privacy policy explains local storage and the optional analytics choice.