A lineup optimizer searches the player pool for the combination of eight players that meets your constraints, such as the $50,000 salary cap and roster slots, and scores best on a target like projected points. It saves hours of manual checking, but it only reflects the inputs and rules you give it. You still make the calls.
What the optimizer solves
Building a lineup by hand is a constrained puzzle. You must fill PG, SG, SF, PF, C, G, F and UTIL, stay at or under $50,000, and pick from dozens or hundreds of players. The number of possible lineups is enormous.
An optimizer treats this as a math problem. It picks the set of players that fits the rules and gives the highest total of whatever you ask it to maximize. A solver does not list every combination. It searches for the best lineup under the constraints and can rule out large groups of lineups at once, so it will not miss a lineup that fits under the cap but that you overlooked.
That strength is also a limit. If your projections are off, the optimizer will confidently build around the error. It does not know a player’s minutes are in doubt unless the inputs say so.
Maximizing projection vs simulating outcomes
The simplest optimizer maximizes total projected points. It picks the best average lineup. That makes sense for cash games, where you want a solid total.
For tournaments, the average is not the target. You want a lineup that has a real chance of a very high score. Some tools simulate many possible outcomes for each player and build lineups that perform well in the upper tail of those simulations. That tends to favor players with wider ranges and games where several players could have big nights together.
Projection inputs matter more than any setting. The optimizer treats every number as truth, so a small error in one player’s minutes can pull an entire lineup toward him. Skim the top of the player pool and fix anything that looks wrong before you build.
Neither approach is guaranteed to produce a better result. They answer different questions. Pick the one that matches the contest.
Locks, excludes and exposure
Controls let you impose your own judgment on the build.
- Lock: a player who must appear in every lineup. Use it for a player you are sure about.
- Exclude (or fade): a player who must not appear in any lineup, for example someone with unclear health.
- Exposure cap: the maximum percentage of lineups a player can appear in, such as 40 percent. This spreads your risk across several lineups.
- Minimum exposure: some optimizers also let you set the least share of lineups in which a player must appear. TipoffLab DFS uses a maximum only; use Lock when you want a player in every lineup.
- Max players per team: a limit on how many players from one team can be in a lineup. A low limit reduces overlap with one game result. A high limit allows stacks.
Building many unique lineups
Multi-entry GPPs let you submit several lineups. If your lineups are nearly identical, they all rise or fall together. Exposure caps force variation. Some optimizers also offer a uniqueness setting, a minimum number of different players between any two lineups. TipoffLab DFS does not have one and relies on exposure caps instead.
Think about your goal. If you like one player strongly, lock him or give him a high exposure. If you are less sure about a group of players, cap each at a lower exposure so a single bad result does not damage every lineup.
A useful method is to start with a small set of locks, add a few excludes for players you do not trust, set exposure caps for everyone else, and then look at the results. If every lineup looks the same, lower the caps. If the lineups look random, raise them or add a lock.
Keep in mind that more lineups mean more entry fees. Stay within a budget you can afford. Paid contests are for adults where legal.
Filling the contest entry file
Most DFS sites let you download a CSV of your entries for a contest. It lists each entry slot. You fill the player columns with the right player IDs and upload the file back.
Doing this by hand across dozens of lineups is slow and error-prone. In TipoffLab DFS you upload your contest entry CSV and download it filled. The tool never asks for your DFS-site login and never enters contests for you. You upload the file yourself.
Before uploading, check a few lineups to confirm the salaries, positions and player IDs look right.
What the optimizer cannot do
An optimizer cannot see news that arrives after its inputs. It cannot read a coach’s mind about minutes. It cannot tell you which of two equal projections to trust. It is a tool that applies your rules at scale.
That means the decisions are still yours. Review the projected minutes for your core players, check the latest injury report before lock, and remove any player you do not trust. Re-run the build after major news.
See it in TipoffLab DFS
Pick the players you believe in, exclude the ones you don't, cap how often anyone appears, and let the builder do the salary-cap math. One lineup for a single-entry contest or a full set for a 150-max tournament.
Hub · OptimizeNov 4, 2026 · sample view- PGJalen BrunsonNYK$8,10046.4
- SGPaul GeorgeBOS$7,20037.9
- SFSaddiq BeyNOP$6,10034.8
- PFOG AnunobyNYK$6,20033.6
- CDeandre AytonWAS$3,30021.8
- GQuenton JacksonIND$4,10025.4
- FAnthony DavisWAS$8,40048.4
- UTILJeremiah FearsNOP$6,60039.7
FAQ
Does an optimizer guarantee a better lineup?
No. It finds the best lineup under the projections and rules you give it. If the projections are wrong, the lineup will reflect that.
What is an exposure cap?
It is a limit on how many of your lineups can include a player. A 40 percent cap on a player means he can appear in at most 40 percent of your lineups.
Why limit players per team?
It controls how much your lineup depends on one team’s game. A lower limit spreads risk. A higher limit lets you build stacks.
Do I give the tool my DraftKings login?
In TipoffLab DFS, no. You upload your contest entry CSV and download it filled, then upload it yourself.