What should I paste from Spark?

Paste the text export or sampler summary Spark gives you. If parsing fails, try a shorter excerpt that still includes the top entries.

Is this the same as Timings?

Spark is the modern profiler most Paper servers use. The reader also accepts simple Timings-style percentage lists when you paste them as text.

Will this lower my TPS automatically?

No. It shows where time is spent so you can change farms, plugins, or distances yourself, then profile again to confirm.

Minecraft Spark & Timings Reader

Paste a Spark or Timings export to see top lag sources — plugins, entities, and chunks — with practical fix tips.

Paste your Spark report

Paste a Spark sampler text export or JSON profile from the Spark mod or plugin. We will highlight what is using the most server time and suggest next steps.

Spark export

Overview

Top time consumers

Ranked by share of sampled server time. Focus on the largest bars first.

Suggestions

Expected format

Spark reports usually include sections like server thread timings, plugins, world, entities, and tick regions. You can paste:

Text copied from the Spark web viewer or in-game /spark profiler export
JSON downloaded from Spark (full profile object)
Simple timing lines such as PluginName: 12.34% or indented tree entries with percentages

Server thread 42.10%
  World tick 18.50%
    Entity tick 9.20%
Plugins (12)
  WorldGuard 3.40%
  Essentials 2.10%
Entities: 842
Tick regions: 4 active

Find what actually causes lag

Guessing whether lag is “entities” or “a plugin” wastes hours. Spark samples where the server spends tick time. This reader turns a text or JSON export into a ranked list of offenders with clear percentages so you know what to trim first.

Load a sample report to learn the layout, then paste your own sampler summary. Focus on the top few entries — fixing the heaviest items usually recovers more TPS than micro-tuning everything else.

Plugins, entities, and chunks

Heavy plugins often show up as their own rows. Entity and farm lag appears as world or entity sections. Chunk and redstone issues surface as tick-region hotspots. The tips panel suggests next steps such as capping farms, lowering simulation distance, or updating a plugin.

Use results together with view-distance and simulation-distance in server.properties. A clean Spark report after a change is the best proof your optimization worked.

How to capture a useful Spark report

Run Spark during a busy period when lag is noticeable, not on an empty test world. Export the sampler or copy the summary Spark prints, then paste it here. If parsing fails, try a shorter excerpt that still includes the top percentage lines.

Always profile on a backup or after a restart with known plugins so you are not chasing a one-off spike from a single event.

Common questions