Dice Rules & Odds Responsible Gambling
Menu

Online vs. Land-Based Dice Games

Online dice games are not all generated in the same way. A physical land-based table uses equipment and procedures at a venue. A live-dealer game delivers a physically conducted process through video and a digital interface. An RNG-based game produces outcomes within software rather than showing a streamed physical roll.

Three dice on a pale green background, introducing a comparison of online and land-based games.

This guide compares delivery characteristics rather than ranking one format as best, safest, or most profitable. Format alone does not determine the rules, house edge, integrity, legality, or likelihood of winning. Wagers, payouts, speed, interface features, and availability can differ by game, product, venue, and jurisdiction.

Editorial role
Dice Rules & Odds editorial team
Research method
Desk research using technical standards, official regulatory material, and ruleset-specific mathematical references
Review status
Editorial and source review completed for this edition; no hands-on operator or venue testing is claimed
Sources checked
GLI-19, National Indian Gaming Commission guidance, the Indian Gaming Regulatory Act, WCAG 2.2, and the mathematical references listed below

Compare the three delivery formats at a glance.

On this page

Essential delivery and integrity terms

Land-based physical table
An in-person game conducted with physical equipment at a venue. The exact equipment, staffing, procedures, wagers, and rules can vary.
Live dealer
A remote format in which a player uses a digital interface connected to a live or physically conducted game process. “Live dealer” describes video delivery and interaction; it is not another name for an RNG game.
RNG
A random number generator used to produce outcomes in digital systems.
PRNG
A pseudorandom number generator: a deterministic algorithm that produces sequences appearing random from an initial state or seed. Whether and how a particular game uses one must be established from product-specific documentation.
Paytable
The documented schedule of payouts for winning outcomes. A valid house-edge calculation requires a defined wager, ruleset, and paytable.
Audit information
Records or documentation that may help evaluate a system or investigate a result, such as game identifiers, timestamps, result histories, software versions, testing reports, or dispute records. What is available differs by implementation.
Technical dependency
A device, network, browser, video system, software service, account system, or other technology needed to access or complete a game session.
Game rules
The conditions that determine valid wagers, outcomes, settlement, pushes, commissions, exceptions, and payouts.
Delivery format
The way the game is presented and operated: at a physical venue, through a live stream, or through a software-generated digital system. A change in format does not necessarily preserve the same rules.

For technical detail about physical randomness, RNGs, PRNGs, laboratory testing, and cryptographic verification, read what game-integrity evidence can and cannot prove.

Physical tables, live dealer, and RNG games compared

Scroll horizontally to view every column.

Neutral comparison of three dice-game delivery formats. Product-specific features may differ.
Comparison point Physical land-based table Live-dealer stream RNG-based digital game
Outcome source A physical roll or another documented physical process at the venue. A physical process delivered remotely through video, subject to the product's documented implementation. An outcome produced within a digital system by an RNG or related implementation.
Player-facing equipment Table layout, dice or other physical equipment, markers, and posted displays. Screen, video stream, game controls, rules display, and account interface. Screen, game controls, rules and paytable interface, and account system.
Typical interaction In-person communication and physical or verbal wager procedures. Remote controls, video, and sometimes text-based communication. Software controls and automated prompts or settlement.
Rules and paytable display May appear on the layout, signage, rule card, or venue documentation. Complete details may require asking staff. May be available in an interface panel or linked rules document. Visibility and completeness are product-dependent. Usually presented in an interface or rules document, but clarity, completeness, and ease of access vary.
Pace control Influenced by venue procedures, staff, and other participants. Influenced by the streamed process, interface timing, and product procedures. Often more automated, but timing, pauses, and speed controls depend on the implementation.
Records or result history May depend on venue systems and procedures; player-facing records are not universal. May include session or result histories, stream records, and game identifiers. Availability and retention vary. May include digital result histories, identifiers, and transaction records. Availability and retention vary.
Accessibility considerations Venue access, table height and reach, noise, lighting, communication, signage, and available accommodations. Keyboard access, video alternatives, captions or text information, contrast, zoom, timeout behavior, and stream quality. Keyboard access, screen-reader support, status announcements, contrast, zoom, reflow, timeout behavior, and control labeling.
Network dependency No player internet connection is normally required for the physical table itself. A stable network connection is needed for video, controls, and result communication. A network may be required for access, account functions, outcome requests, and records, depending on the system.
Device dependency Primarily venue equipment rather than a personal device. A compatible device, browser or application, display, and input method are generally required. A compatible device, browser or application, and input method are generally required.
Human process dependency High: equipment handling, supervision, wager acceptance, and settlement may involve staff. Both human and technical: the physical process and staff are combined with video and software systems. Settlement and presentation are primarily software-controlled, though operation, support, security, and oversight still involve people.
Integrity evidence to seek Venue procedures, equipment controls, written rules, regulator information, and dispute procedures. Physical-process documentation, written rules, result-recording procedures, connection rules, licensing, and relevant system testing. Outcome-generation description, written rules, regulator information, testing reports or certifications where public, version details, and dispute procedures.
Licensing questions Which commercial or tribal authority regulates the venue and game? Which authority licenses the operator and authorizes this online activity for the player's location? Which authority licenses the operator, system, and activity, and is the game authorized in the player's location?

Conclusion: Delivery format does not determine house edge, legality, or integrity. A visible physical roll may make part of the outcome process easier to observe, while an RNG system may have technical testing information. Neither observation nor testing proves that the paytable is favorable. Randomness, payout value, licensing, legal availability, and player profitability require separate evidence.

Gaming laboratory standards can include technical and statistical requirements for interactive gaming systems and RNGs. Passing such testing does not guarantee a win or positive expected value. Likewise, a game appearing in a global product catalog does not establish that it is available or lawful in a particular U.S. jurisdiction.

Use the format verification checklist before relying on a format-specific claim.

Land-based physical dice tables

A land-based table places the equipment, staff, and participants in an in-person venue. Depending on the game, the visible setup may include dice, a table layout, markers, displays, and procedures for placing and settling wagers. Those procedures are not necessarily identical across every venue.

Seeing physical equipment does not establish that a wager has favorable value, that the game is authorized everywhere, or that every applicable rule is visible on the layout. House-edge analysis still requires the exact wager, rules, payout, commission, push treatment, and calculation denominator.

What to verify at the venue

  • The complete posted or written game rules.
  • The paytable and whether payout figures mean net winnings or total return.
  • Any commissions, fees, push rules, exceptions, or attached-wager requirements.
  • Wager limits when they affect whether a rule or supplemental wager is available.
  • The procedure used to resolve unclear rolls or disputes.
  • The commercial, tribal, or other authority responsible for the venue.
  • The minimum age and permitted activity for that venue and jurisdiction.

Four separate verification layers

  1. Physical equipment: Identify what produces or displays the result.
  2. Written rules: Check how the result affects the exact wager.
  3. Venue procedures: Check handling, settlement, exceptions, and disputes.
  4. Regulatory authority: Identify who oversees the venue and activity.

Accessibility also depends on the specific venue. Relevant factors may include entrances and routes, table height, reach, lighting, noise, communication practices, readable rules, and available accommodations. A physical setting should not be assumed either accessible or inaccessible without checking its actual design and procedures.

Practical next step: Check the posted rules and identify the venue's regulator before drawing conclusions about payouts or authorization.

Live-dealer dice games

A live-dealer dice game combines a physically conducted game process with remote digital delivery. A player generally views video and uses an interface for actions such as selecting a wager, reading the rules, seeing a result, or reviewing account information. Exact implementations require product-specific documentation.

The physical result process and the digital delivery system should be evaluated separately. A visible stream can show part of a game, but software still handles functions such as video transmission, input timing, wager acceptance, result display, settlement, account access, and records.

Live-dealer layers to examine

  1. Physical game process: What equipment and procedure produce the result?
  2. Video transmission: Is the process sufficiently clear, continuous, and understandable?
  3. Game interface: How are actions accepted, timed, confirmed, and settled?
  4. Rules and paytable: Which written document controls if the display and video appear inconsistent?
  5. Records and disputes: How is a result identified, recorded, reviewed, and challenged?
  6. Licensing and location: Which authority authorizes the operator and activity for the relevant jurisdiction?

Verify connection-loss and interruption procedures before relying on the format. The written rules should explain what happens if video freezes, an input is delayed, a session disconnects, or the displayed result differs from an account record.

A visible stream does not by itself prove favorable payouts, full system integrity, legal availability, or guaranteed winnings. Pace and interaction also vary by product; they should not be treated as universal features of all live-dealer games.

Six separate evidence layers for dice-game integrity: outcome generation, technical implementation, testing, rules and paytable, legality and licensing, and player results.

The physical process, video and interface implementation, technical verification, paytable, license, and individual result are separate layers. Evidence about one layer does not automatically prove claims about the others. In particular, a visible or verified outcome process does not establish favorable payouts, legal availability, or guaranteed winnings.

Practical next step: Verify the written rules, result-recording method, connection procedures, dispute policy, and licensing authority.

RNG-based digital dice games

In an RNG-based game, the displayed outcome is produced within a digital system rather than observed from a streamed physical roll. The interface may visually represent dice, but that presentation does not necessarily describe the underlying outcome-generation method.

An RNG or PRNG implementation can be evaluated through technical and statistical testing. GLI-19, for example, contains standards relevant to interactive gaming systems and random number generation. The existence or successful completion of testing does not establish that the paytable favors the player, that the game is lawful in every location, or that any individual will win.

Documentation to seek

  • The complete rules and named paytable.
  • A description of how outcomes are generated, stated at an appropriate level for the product.
  • The regulator or licensing authority and a way to verify the relevant record.
  • Testing information, laboratory details, certification references, or software-version information when publicly available.
  • Result-history and game-identifier information.
  • Dispute, interruption, and connection-loss procedures.
  • Any rules governing updates or changes to the software or paytable.

Conceptual outcome flow

  1. A player or system initiates a permitted game action.
  2. The documented digital system obtains or generates an outcome.
  3. The game's rules and paytable are applied to that outcome.
  4. The interface displays the result and settlement.
  5. Relevant records may be stored according to the implementation and regulatory requirements.

This is a conceptual sequence, not a claim that every system uses one architecture. Product documentation and applicable technical standards are needed for implementation-specific conclusions.

A short personal result history cannot validate or invalidate an RNG. Independent outcomes can naturally include streaks, and previous outcomes do not make a future result due.

Read the detailed guide to RNGs, PRNGs, testing, and game-integrity evidence for the technical distinctions this comparison does not reproduce.

The same game name does not guarantee the same rules

Hypothetical verification scenario: Suppose three products are all labeled “craps”: one at a physical table, one delivered through a live stream, and one generated by RNG software. The shared name is not enough to establish that their wagers, payouts, settlement rules, or regulatory status match.

Scroll horizontally to view every column.

Questions to ask when comparing hypothetical craps implementations
Rule or procedure Physical table Live dealer RNG game
Point rules Read the table and venue rules; do not assume standard or crapless rules from appearance alone. Check the written rules controlling the streamed game. Check the software's written rules rather than relying on visual resemblance to a table.
Available wagers Confirm which contract, proposition, place, and supplemental wagers are actually offered. Confirm the wagers enabled in the interface and any timing restrictions. Confirm the software's wager menu and any automated dependencies.
Odds limits Ask what multiple or maximum applies to attached odds. Check the interface and written limit rules. Check the software rules and whether limits vary by point or game mode.
Payout wording Determine whether displayed figures describe net winnings or total returns. Compare the interface display with the controlling written paytable. Review the paytable and settlement examples.
Commissions and exceptions Check when and how commissions are collected and how pushes are handled. Check automated deductions, timing, and exception rules. Check software settlement rules, deductions, pushes, and rounding.
Result records Ask how a disputed physical result is documented. Check for game identifiers, stream records, and account history. Check for result identifiers, transaction records, and account history.
Disputes Identify the venue process and regulator. Check the operator process, connection rules, and licensing authority. Check the operator process, technical records, and licensing authority.

No house-edge comparison is valid until the exact wager, ruleset, paytable, commissions, push treatment, and calculation denominator are matched. For example, a true-odds craps wager can have a standalone house edge of 0% when paid at true mathematical odds, but it requires an underlying contract wager with an expected cost. That fact does not make the combined game a zero-cost proposition.

Use the standard Craps guide to compare round and wager rules, but continue to rely on the implementation's own written documentation for product-specific conclusions.

Rules, paytables, and pace must be evaluated separately

A faster or more automated delivery format does not change the mathematical probability of an outcome unless the rules, outcome process, or paytable also change. It can, however, allow more wagering decisions or resolved rounds over a period. When a wager has negative expected value, greater total exposure generally means greater expected loss in dollar terms, even though short-term results remain uncertain.

Three concepts that should not be combined

Delivery speed
How quickly actions and rounds are completed. It describes pace, not payout value.
Hit rate
How often a wager produces a winning result. A frequent win can still be too small to offset less frequent losses.
Expected value and house edge
Expected value is the probability-weighted average net result across all outcomes. House edge is the average expected player loss as a percentage of the specified initial wager under stated rules and payouts. It is not the probability of losing one round.

Before comparing value, check whether the paytable states net winnings or total return, and identify commissions, pushes, triple exceptions, attached wagers, settlement rounding, and other conditions. A house-edge figure is not meaningful without a complete paytable.

Use the dice-game paytable audit checklist to inspect payout wording and exceptions. For the mathematics behind hit rate, expected value, and house edge, see Dice Probabilities, Expected Value and House Edge.

Accessibility and technical dependencies

Accessibility is a core comparison criterion, not a secondary convenience. No delivery format is universally more accessible. The relevant question is whether the specific venue, stream, or interface meets a person's access requirements.

WCAG 2.2 is a W3C Recommendation for web accessibility. Its principles are relevant to digital controls, rules, disclosures, tables, status messages, and account interfaces, but a product should not be assumed conformant without supporting evidence.

Physical venue checklist

  • Can the venue and table be reached and used without avoidable physical barriers?
  • Are table information and written rules readable at the required distance and zoom equivalent?
  • Can rules, results, and procedures be communicated without relying on sound alone?
  • Are lighting, noise, table height, reach, and time pressure compatible with the user's needs?
  • What accommodations or alternative communication methods are available?

Live-stream checklist

  • Can all controls be operated with a keyboard or suitable alternative input?
  • Do zoom and reflow preserve the rules, controls, video information, and result display?
  • Are important spoken or visual details also available as captions, text, or status announcements where relevant?
  • Are focus, contrast, timing, and error states clear?
  • What happens if the stream freezes, becomes unclear, or disconnects?
  • Can written rules and dispute procedures be reached without depending on video?

RNG-interface checklist

  • Are controls, wager names, results, and account messages labeled for assistive technology?
  • Does the interface work with keyboard input, high zoom, narrow viewports, and text resizing?
  • Are result changes and errors announced without relying on animation or color alone?
  • Can timeouts be extended or understood before they occur?
  • Are the full rules and paytable available in an accessible text format?
  • Are interrupted-session and connection-loss rules clearly explained?

Online access also depends on the device, operating system, browser or application, network quality, authentication process, and compatibility with assistive technology. Check the specific implementation before relying on general accessibility claims or badges.

Licensing and availability depend on jurisdiction

General educational information, not individualized legal advice: Lawful land-based casino gaming does not automatically mean lawful online casino gaming. U.S. gambling law cannot be reduced to one nationwide yes-or-no rule.

Commercial, tribal, land-based, and online gaming can operate under different state, federal, tribal, and compact frameworks. Indian tribes are the primary regulators of Indian gaming. The National Indian Gaming Commission regulates Class II gaming and aspects of Class III gaming, while Class III regulation may also be addressed through tribal-state compacts. Minimum age can vary by state, activity, venue, and tribal jurisdiction.

Five-step verification workflow

  1. Identify the location and jurisdiction. Determine the player's location and whether the venue or activity falls under state, tribal, federal, or another relevant authority.
  2. Identify the activity and delivery format. Distinguish a physical casino game from online casino play, live-dealer delivery, or another activity.
  3. Find the official authority. Use current state, tribal, compact, or federal sources rather than an advertisement or general product catalog.
  4. Verify the venue or operator. Check the applicable official license or authorization record where one is available.
  5. Confirm the game and age rules. Verify that the specific activity and game type are authorized and determine the minimum age that applies.

Record the official source URL and the date checked. Do not infer U.S. availability from a foreign rulebook, a provider's global catalog, or the fact that a similarly named game is offered elsewhere.

Because laws, licenses, compacts, and market availability can change, confirm current details with the relevant authority.

Follow the complete U.S. regulator-verification workflow for licenses, game types, online availability, and minimum age.

Checklist for evaluating a dice-game format

Identify the implementation

  • Record the exact game name and delivery format.
  • Determine where and how the outcome is generated.
  • Do not assume that a physical-looking interface represents a physical roll.

Check rules and payout value

  • Obtain the complete written rules and named paytable.
  • Check payout wording, commissions, fees, pushes, exceptions, rounding, and attached-wager requirements.
  • Match any numerical claim to a named wager, ruleset, paytable, denominator, source, and verification date.
  • Do not treat a high hit rate as proof of favorable expected value.

Check integrity information

  • Identify the evidence relevant to the outcome process: physical procedures, video records, RNG testing, or another documented method.
  • Look for testing or certification details where relevant and publicly available.
  • Do not treat integrity testing as proof that payouts favor the player.
  • Do not use a short personal result history to judge randomness.

Check licensing and procedures

  • Identify the official regulator or licensing authority.
  • Verify the venue or operator where an official record is available.
  • Confirm that the delivery format and game type are authorized for the relevant location.
  • Check result-history, dispute, interrupted-session, and connection-loss procedures where applicable.

Check access and technology

  • Identify necessary venue accommodations or device, browser, application, network, and account requirements.
  • Check keyboard access, zoom, reflow, contrast, status announcements, timing, and written-rule availability as relevant.
  • Confirm that the format remains understandable if video, animation, sound, or color is unavailable.

Record the evidence

  • Save the source title, organization, URL, ruleset or version, and date checked.
  • Separate conclusions about randomness, payout value, licensing, legality, accessibility, and possible player results.
  • Do not infer legality or availability from advertising, a global catalog, or a foreign rulebook.

If the unanswered question concerns outcome testing, continue to the game-integrity guide. If it concerns authorization or licensing, use the U.S. legal-verification guide.

Changing the format does not remove gambling risk

Comparison method, assumptions, and sources checked

Methodology ledger

Physical-table definition
An in-person game using physical equipment and venue procedures.
Live-dealer definition
A remotely accessed interface connected to a live or physically conducted game process.
RNG-based definition
A digital implementation in which the outcome is produced within a software system rather than observed from a streamed physical roll.
Comparison method
Formats were compared by outcome source, equipment, interaction, rule display, pace, records, accessibility, technical dependencies, human procedures, integrity evidence, and licensing questions.
Assumptions
Pace, controls, records, accessibility features, available wagers, and dispute procedures were treated as implementation-dependent rather than universal.
Technical source
GLI-19 was used as a technical source for standards relevant to interactive gaming systems and RNGs. This page does not claim that any particular product has passed GLI testing.
Legal-source boundary
Official authorities and statutory material were used for high-level jurisdictional distinctions. No permanent state-by-state legality conclusion is made here.
Review type
Desk research and editorial comparison. No operator testing, venue inspection, account use, or hands-on product review is claimed.
Editorial review status
Reviewed for ruleset specificity, technical scope, legal caution, accessibility language, and separation of randomness from payout value.
Material correction history
No material corrections are recorded for this edition.

Primary and technical sources

Secondary checks

For the site's complete source hierarchy, calculation standards, and correction policy, read Editorial Standards and Calculation Methodology. That page also provides the approved route for reporting a factual, technical, legal, sourcing, or accessibility error.