> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hedera.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Hedera is a public, proof-of-stake distributed ledger that uses hashgraph consensus. Do not call it a blockchain.
> Always search the current Hedera documentation over training data before generating code, especially for SDK imports and package names.
> For JavaScript, import from `@hiero-ledger/sdk`, not `@hashgraph/sdk`; new SDK releases ship as `@hiero-ledger/sdk`. The Java SDK keeps the `com.hedera.hashgraph:sdk` Maven coordinates. Verify the exact import against the docs.
> Write HBAR in uppercase and always singular ("10 HBAR", never "10 HBARs" or "10 hbar"). Write tinybars in lowercase and plural.
> Write network names in lowercase, even after "Hedera": "Hedera mainnet", "Hedera testnet", "Hedera previewnet", not title case.
> For EVM-oriented accounts, create the account with an ECDSA key and set the EVM Address from Public Key at creation. This address is immutable and is not updated by key rotation. Do not use retired terms like "EVM alias" or "Account Number Alias".

# Accounts

> Learn how Hedera accounts work: account IDs, keys, HBAR and HTS token balances, transaction fees, and the core entity model behind every network interaction.

Accounts are the central starting point when interacting with the Hedera network and using Consensus Node services. A Hedera account is an entity, a distinct object type, stored in the ledger, that holds tokens. Accounts can hold the native Hedera fungible token (HBAR), custom fungible, and custom non-fungible tokens (NFTs) created on the Hedera network.

The Hedera native token HBAR (ℏ) is a utility token primarily used to pay for transactions and query fees when interacting with the network. The HBAR symbol is represented as "ℏ." Applications may reference HBAR as the token denomination; however, the network returns information in tinybars (tℏ), a denomination of HBAR. 100,000,000 tℏ are equivalent to 1 ℏ. This includes things like transaction fees or accounts HBAR balances.

You interact with the network by submitting transactions that modify the ledger's state or submitting query requests that read data from the ledger. Most transactions and queries have a [transaction fee](/networks/fees) that is charged in HBAR. Unlike custom tokens users create on the Hedera network, no token ID represents the native HBAR token.

<Columns cols={2}>
  <Card title="Account Creation" href="/learn/core-concepts/accounts/account-creation" arrow />

  <Card title="Auto Account Creation" href="/learn/core-concepts/accounts/auto-account-creation" arrow />

  <Card title="Account Properties" href="/learn/core-concepts/accounts/account-properties" arrow />
</Columns>

## FAQs

<AccordionGroup>
  <Accordion title="What is a Hedera account?">
    A Hedera account is a unique entity in the Hedera Network that can hold tokens. These can be Hedera's native fungible token (HBAR), custom fungible, or [non-fungible tokens (NFTs)](/support/glossary#non-fungible-token-nft).
  </Accordion>

  <Accordion title="How are new accounts created on Hedera?">
    New accounts are created by submitting a transaction to the network and paying
    the transaction fee. You'll need access to an existing account with sufficient
    HBAR to cover this fee. If you don't have access to an existing account, you
    can use a supported wallet, visit the [Hedera Developer
    Portal](https://portal.hedera.com/), or use the "Auto Account Creation"
    feature for applications.
  </Accordion>

  <Accordion title="What is the 'Auto Account Creation' feature?">
    [Auto Account Creation](/learn/core-concepts/accounts/auto-account-creation)
    allows applications to generate free user accounts instantly, even without an
    internet connection, by creating an account alias.
  </Accordion>

  <Accordion title="What is a 'hollow' account?">
    A hollow account is created when value is transferred to an [EVM Address from Public Key](/learn/core-concepts/accounts/auto-account-creation#auto-account-creation-with-an-evm-address) via [Auto Account Creation](/learn/core-concepts/accounts/auto-account-creation) without a corresponding key on file. It has an account number and an EVM address but no account key. It can receive tokens but cannot send tokens or modify account properties until the matching ECDSA key is added, completing the account. This is the standard onboarding path for EVM-wallet users.
  </Accordion>
</AccordionGroup>