Browser operations

1. Connect to a Neo4j DBMS

Neo4j Browser is the easiest way to access a Neo4j database. To establish a connection, you enter the DBMS URL, the name of the database you want to connect, and the user credentials. You can also use the :server command to manage the connection to Neo4j. For more information, see Manage connection commands.

home screen

1.1. Connection URI schemas

By default, Neo4j Browser communicates with a Neo4j DBMS via the Bolt Protocol using the Neo4j JavaScript Driver to execute Cypher queries. However, it is possible to turn off Bolt and use HTTP(S) instead, as in older versions of Neo4j Browser.

Neo4j Browser supports the following connection URI schemas:

  • neo4j://(unencrypted) and neo4j+s:// (encrypted with TLS) — work on either a single instance or a cluster. Routing is handled by the driver. If used on a cluster, it routes to a cluster member, not necessarily the system at the IP that you specified. Queries executed over that protocol route according to the transaction functions --write transactions go to the leader and read transactions route between followers and read replicas.

  • bolt://(unencrypted) and bolt+s:// (encrypted with TLS) — connect only to the server with the IP you specify. It does not route anywhere else. All queries over this protocol go only to this machine, whether they are read or write queries. Write queries error out if not being sent to the Cluster leader.

If used on a single server (not a cluster), then queries over them will behave identically. A difference in the behavior in neo4j:// and bolt:// is seen only if addressing a cluster member.

For more information on the different connection scenarios, see Connection scenarios. For more information on how to configure connectors (Bolt, HTTP, and HTTPS) for Neo4j and the default ports, see Operations Manual → Configure connectors and Operations Manual → Ports.

1.2. Manage connection commands

The :server command lets you manage the connection to Neo4j, such as connecting, disconnecting, and viewing metadata for the current connection.


:server <action>

  • :server status — Connection status. This is your current connection information.

  • :server change-password — Opens the frame Password change, where you can change your current password.

  • :server connect — Opens the frame Connect to Neo4j. If connected to the server, the frame shows the current user and the connection URL. Otherwise, enter the name of the database you want to connect, the DBMS URL, and the user credentials.

  • :server disconnect — Opens the frame Disconnected, which shows that the current user is disconnected from the server. Then, it runs the :server connect automatically.


:help server user - opens the frame User admin.

1.3. Connection scenarios

Table 1. Neo4j Browser - Bundled with Neo4j
Cluster configured TLS encryption URI



bolt:// or neo4j://



bolt+s:// or neo4j+s://







yes (connect to one specific cluster member only)



yes (connect to one specific cluster member only)



If you are developing on your local machine with a single instance:

  • Default URL to Neo4j Browser is http://localhost:7474/browser (use your web browser).

  • Default connection URL to Neo4j is bolt://localhost:7687.

Table 2. Neo4j Browser - Neo4j Desktop application
Cluster configured TLS encryption URI



bolt:// or neo4j://



bolt+s:// or neo4j+s://







yes (connect to one specific cluster member only)



yes (connect to one specific cluster member only)



Table 3. Neo4j Browser - Web application
Cluster configured TLS encryption URI



bolt+s:// or neo4j+s://




yes (connect to one specific cluster member only)



Neo4j Browser is available as a web application at

Neo4j Browser - Sandbox

In Neo4j sandbox, you can launch a Neo4j Browser web application by clicking Open with Browser. It automatically connects with a connection URL similar to:


Neo4j Browser - Neo4j Aura

In the Neo4j Aura console, Neo4j Browser can be accessed as a web application within the user interface. The Neo4j Browser web application connects to your Neo4j instance without having to enter any connection URL.

The connection URL is similar to:


Each database has a dbid that can be inferred from the Aura Console.

The URL https://<dbid> can also be used to access Neo4j Browser for that specific dbid on Neo4j Aura.

2. Browser credentials handling

Neo4j Browser has two mechanisms for avoiding users having to enter their Neo4j credentials repeatedly.

First, while the Browser is open in a web browser tab, it ensures that the existing database session is kept alive. This is subject to a timeout. The timeout is configured in the setting browser.credential_timeout. The timeout is reset whenever there is user interaction with the Browser.

Second, the Browser can also cache the user’s Neo4j credentials locally. When credentials are cached, they are stored unencrypted in the web browser’s local storage. If the web browser tab is closed and then re-opened, the session is automatically re-established using the cached credentials. This local storage is also subject to the timeout configured in the setting browser.credential_timeout. In addition, caching credentials in browser local storage can be disabled altogether. To disable credentials caching, set browser.retain_connection_credentials=false in the server configuration.

If the user issues a :server disconnect command, any existing session is terminated, and the credentials are cleared from the local storage.

3. Adjust Browser settings

The Neo4j Browser defaults for all settings can be adjusted at any time in Neo4j Browser and globally.

To view all currently configured settings, run :config.

Example 1. Show the configuration settings
Example output
  "maxHistory": 20,
  "theme": "auto",
  "initCmd": ":play start",
  "playImplicitInitCommands": true,
  "initialNodeDisplay": 300,
  "maxNeighbours": 100,
  "showSampleScripts": true,
  "browserSyncDebugServer": null,
  "maxRows": 1000,
  "maxFieldItems": 500,
  "shouldReportUdc": true,
  "autoComplete": true,
  "scrollToTop": true,
  "maxFrames": 30,
  "codeFontLigatures": true,
  "useBoltRouting": false,
  "editorLint": false,
  "useCypherThread": true,
  "enableMultiStatementMode": true,
  "connectionTimeout": 30000,
  "showPerformanceOverlay": false
Table 4. Available Browser settings
Browser Setting Default value Description Configurable in the Browser Settings drawer



The maximum number of recently executed queries kept in Browser. When reached, old entries get retired. The command history is persisted across Browser restarts.




Neo4j Browser UI theme. Possible values: auto, normal, outline, and dark.



:play start

The initial command that is run when connected to the graph.




If true, Browser automatically runs the command set in initCmd on startup, for example :play start.




Limit the number of nodes displayed on the first load of the graph visualization.




The maximum number of neighbours for a node.




Whether to display the Sample Scripts tab in Favorites.




Internal setting, used for debugging Browser Sync.




The maximum rows to render in the Table and Text result views.




Limit the length of the returned lists. For example, if a node has 1000 labels, the list will be cut off to the value set in maxFieldItems.




Report less user metrics (user data collection).




Automatic completion of missing relationships.
When you execute a query, any relationships not explicitly returned by the query, but that exist between the nodes will be shown in the graph. You can disable for queries where it is important to see only the relationships the query returns. This behavior is controlled by the Connect result nodes in Browser Settings.




Automatically scroll stream to top on new frames.




The maximum number of result frames. When reached, old frames get retired.




Allow font ligatures for the Cypher editor bar and Cypher snippets.




Whether to use Bolt routing. The Bolt+routing feature on Neo4j drivers discovers a cluster member (drivers have a load-balancing feature).




Enable/disable squiggly lines under text.




Run Cypher queries through a web worker (background thread) to increase performance.




Allows you to write and edit multi-line queries (use a semicolon (;) to separate statements).




The timeout in ms when establishing a connection to Neo4j.




Internal setting, used for showing a performance overlay (FPS and memory usage).




Trigger autocomplete when typing.


3.1. Adjust settings in Browser

To change the configuration settings locally in Neo4j Browser, you can either use the tabs in the Browser Settings drawer or, in the Cypher editor, type the command :config together with the setting and the new value.

Example 2. Adjust an individual setting

The example shows how to change the maximum number of neighbors for a node.

:config maxNeighbours:100
Example 3. Adjust several settings

The example shows how to change the maxFrames from its default of 50 to 10 and the theme to outline.

:config {maxFrames: 10, theme: "outline"}

After making the change, re-running :config reports that maxFrames has been set to 10, and the theme is defined to outline. The Browser Settings drawer also reflects this change.

Adjusting the settings first resets the configuration to the default configuration and then sets the given configurations.

3.2. Adjust settings globally

To change the configuration settings for all users of Neo4j Browser, modify the neo4j.conf file, or if using Neo4j Desktop, navigate to the DBMS which settings you want to update, click the ellipsis dropdown menu, and select Settings.

For example, to change the maxFrames from its default of 50 to 10 and the theme to outline, add the following line to neo4j.conf:

browser.post_connect_cmd=config {maxFrames:10, theme: "outline"}

This changes the maxFrames from its default of 50 to 10 and then restarts Neo4j.

Table 5. Global Browser settings
Browser Setting Default value Description



Configure the policy for outgoing Neo4j Browser connections.



Configure the Neo4j Browser to time out logged-in users after this idle period. Setting this to 0 indicates no limit. Valid units are ns, μs, ms, s, m, h, and d; default unit is s).


Commands to be run when Neo4j Browser successfully connects to the server. Separate multiple commands with a semicolon (;).


Whitelist of hosts for the Neo4j Browser to be allowed to fetch content from.



Configure the Neo4j Browser to store or not store user credentials.



Configure the Neo4j Browser to store or not store editor history.

4. Start with Browser

When you first open Neo4j Browser and connect to a Neo4j DBMS, it automatically executes the command :play start.
The :play start command outputs an entry page containing interactive guides that you can use to learn some Neo4j concepts, try Neo4j with live data (MovieGraph), and write some basic Cypher queries.
Besides, you can also navigate to the Help & Learn drawer in the sidebar, where you will find more information about useful commands, a lot of built-in guides, and links to documentation.

If you want to change the initially executed command, navigate to the Browser Settings drawer in the sidebar and add a new value for the Initial command to execute setting.

For more information on how to enter and run Cypher queries and commands, see Cypher editor.
For more information about Cypher, see Cypher Manual and Neo4j Cypher Refcard.

5. Visualize results

There are a variety of ways to view data in Neo4j Browser. All queries that you run in the Cypher editor populate a reusable result frame. Query results are rendered as:

  • Visual graph

  • Table

  • Plain text table

  • JSON

You can switch between those with the icons on the left side of the result frame.

If you cannot see the result, you might be in Graph mode but had your query return tabular/scalar data. To see the results, switch the mode to the Table view.

5.1. Graph

The graph visualization functionality is designed to display a node-graph representation of the underlying data stored in the database in response to a given Cypher query. It shows circles for nodes and lines for relationships, and is especially useful for determining areas of interest or quickly assessing the current state and organization of the data.


Handy tips
  • Enable zoom in and out of your graph by entering into fullscreen mode.

  • Expand and remove nodes from the visualization by clicking a node. It gets a halo, where you can dismiss a node, expand/collapse child relationships, or unlock the node to re-layout the graph. Double-clicking a node expands its child relationships.

  • If you cannot see the whole graph or the results display too close together, you can adjust by moving the visual view and dragging nodes to rearrange them.

  • To move the view to see more parts of the graph, click an empty spot within the graph pane and drag it.

  • To rearrange nodes, click and drag them around.

  • The nodes already have sensible captions assigned by the browser, which auto-selects a property from the property list to use as a caption. You can see all the properties of that element if you click any node or relationship. Properties appear below the visualization.

  • Larger property sets might be collapsed into a subset, and there is a little triangle on the right to unfold them. For example, if you click one of the Movie nodes in the MovieGraph (:guide movie graph), you can see its properties below the graph visualization. The same applies to Actor nodes and the ACTED_IN relationships.

5.2. Table

The Table result view displays the result in a table format. It also reports the query time, including the actual query execution time, latency, and deserialization costs.


Even if you feel that the relationship is not hard to find in the tabular format, imagine if you have a graph containing the entire filmography careers of these persons and hundreds of other actors, directors, and film crew members. The connections could easily be lost in a non-visual presentation.

5.3. Text

The Text result view displays the result as a plain text table. It also reports the query time, including the actual query execution time, latency, and deserialization costs.


5.4. Code

The Code result view displays the submitted request, the Neo4j Server version and address, and the response. It also reports the query time, including the actual query execution time, latency, and deserialization costs.


6. Export results

You can download your query results using the down-pointed arrow on the right side of the result frame. The following download options available:

Download the result from the Graph view

Export graph

Download the result from the Table, Text, and Code views

Export table

The Save as project file is available only in Neo4j Desktop. For more information, see Project files.

7. Style Neo4j Browser Visualization

You can customize your graph query result either in place or by using Graph Stylesheet (GraSS).

7.1. Style your graph visualization in place

Neo4j Browser also provides functionality for styling with color and size, based on node labels and relationship types.

If you click any label or relationship above the graph visualization, you can choose its styling in the area below the graph. Colors, sizes, and captions are selectable from there. To see this for yourself, you can click the Movie label above the graph and change the color, size, and captions of all nodes labeled with Movie. The same applies to the relationship ACTED_IN.

Changes to nodes labeled Movie

style movie node

Changes to relationships labeled ACTED_IN

style actedin relationship

7.2. Style your graph visualization using a GraSS file

Alternatively, follow the steps to customize your styles by importing a graph stylesheet (GraSS) file for Neo4j Browser to reference.

  1. Run the command :style and download your current graph style by using the Export GraSS option.

    Neo4j supports both CSS and JSON format as a .grass file contents.

    Example 4. Sample of a .grass file contents
    node {
      diameter: 50px; (1)
      color: #A5ABB6; (2)
      border-color: #9AA1AC;  (3)
      border-width: 2px; (4)
      text-color-internal: #FFFFFF; (5)
      font-size: 10px;
    relationship {
      color: #A5ABB6;
      shaft-width: 1px; (6)
      font-size: 8px;
      padding: 3px;
      text-color-external: #000000;
      text-color-internal: #FFFFFF;
      caption: "<type>"; (7)
    node.* {
      color: #C990C0;
      border-color: #b261a5;
      text-color-internal: #FFFFFF;
      defaultCaption: "<id>";
    node.Status {
      color: #F79767;
      border-color: #f36924;
      text-color-internal: #FFFFFF;
      defaultCaption: "<id>"; (8)
      caption: "{name}";
    node.Person {
      color: #DA7194;
      border-color: #cc3c6c;
      text-color-internal: #FFFFFF;
      defaultCaption: "<id>";
      caption: "{name}";
    node.Movie {
      caption: "{title}";
    1 Diameter of a node circle.
    2 The color of the circle.
    3 The color of the circle border.
    4 The width of the circle border.
    5 The color of the text that is displayed.
    6 Diameter of a relationship circle.
    7 The text that is displayed.
    8 The default caption if no specific caption is set.

    If a node has 2 styled labels, only the first (closest to top) style is applied. If a node does not have a label that is in the GraSS, node is used as the default. Same applies to relationships.

  2. Edit the downloaded file locally using your favourite editor and use drag & drop it to the designated drop area.

The GraSS parser is open source.

8. Neo4j query parameters

Neo4j Browser supports querying based on parameters. It allows the Cypher query planner to re-use your queries instead of parse and build new execution plans.

Parameters can be used for:

  • literals and expressions

  • node and relationship IDs

Parameters cannot be used for the following constructs, as these form part of the query structure that is compiled into a query plan:

  • property keys

  • relationship types

  • labels

Parameters may consist of letters and numbers and any combination of these but cannot start with a number or a currency symbol.

For more details on the Cypher parameters, see Cypher Manual v.4.3 - Parameters.

8.1. Set query parameters

You can set a parameter to be sent with your queries by using the :param command. Using parameters rather than hard-coded values allows for the reuse of the query plan cache.

The :param name => 'Example' command defines a parameter named name, which will be sent along with your queries.
The right hand side of is sent to the server and evaluated as Cypher with an implicit RETURN in front. This gives better type safety since some types (especially numbers) in JavaScript are hard to match with Neo4j:s type system. To see the list of all currently set query parameters and their values, use the :params command. For more information on how to use the commands, see :help param and :help params.

If you are using a multi-database DBMS, parameters cannot be declared when using the system database. Switch to a different database and declare, then switch back to the system database and use them.

Example 5. Set a parameter as an integer
:param x => 1
Example 6. Set a parameter as a float
:param x => 1.0
Example 7. Set a parameter as a string
:param x => "Example"
Example 8. Set a parameter as an object
  1. Map

    :param obj1 => ({props: {name: "Tom Hanks", born:1956}})
    The obj1 parameter
    $obj1 = {"props": {"name": "Tom Hanks", "born": 1956}}

    Maps like {x: 1, y: 2} must be wrapped in parentheses ({x: 1, y: 2}).

  2. List

    :param obj2 => [1, 2, 3, 4]
    The obj2 parameter
    $obj2 = [1, 2, 3, 4]
Example 9. Cypher query example with a parameter
:param name => 'Tom Hanks';
MATCH (n:Person)
WHERE = $name

To run this example, in the Browser Settings drawer, check Enable multi statement query editor. Note that you do not see the output as you are used to when you run multiple statements. In Neo4j Browser, the current state of multi-statement is to set up your environment with multiple statements so that you can execute queries and examine the results, one by one. Alternatively, you can run the :param command separately from the MATCH query.

8.2. Cypher result

It is possible to save the result from a Cypher query to a parameter.

The syntax is:

:param <parameter_name> => { CYPHER STATEMENT }
Example 10. One row returned

This example shows a result of one record returned.

:param result1 => { RETURN 1 AS foo }
The result1 parameter
$result1 = [{foo: 1}]
Example 11. Several rows returned

This example shows a result of three records returned.

:param result2 => { UNWIND [1, 2, 3] AS nbr RETURN nbr }
The result2 parameter
$result2 = [{"nbr": 1}, {"nbr": 2}, {"nbr": 3}]}
Example 12. One row with a node returned
:param result3 => { MATCH (n) WHERE = "Example" RETURN n }
The result3 parameter
$result3 = [{"n": {"identity": 4, "labels": [], "properties": {"name": "Example"}}}]

8.3. Destructuring

It is possible to pick individual values from your result using destructuring and set a specific parameter to a specific value.

The syntax is:

:param [{<returned_parameter>: <parameter_name>, ...}, ...] => { CYPHER STATEMENT }
Example 13. One row returned
:param [{foo}] => { RETURN 1 AS foo }
$foo = 1
Example 14. Rename destructured parameter
:param [{foo: bar}] => { RETURN 1 AS foo }
$bar = 1
Example 15. Syntax
:param [{foo1: bar1, foo2: bar2}] => { RETURN 1 AS foo1, 2 AS foo2 }
$bar1 = 1
$bar2 = 2
Example 16. Several rows returned
:param [{nbr: x}] => { UNWIND [2, 3, 1] AS nbr RETURN nbr ORDER BY nbr ASCENDING }
$x = 1
:param [nbr, nbr, nbr] => { UNWIND [2, 3, 1] AS nbr RETURN nbr ORDER BY nbr ASC }
$nbr = 3
:param [{nbr: x}, nbr, nbr] => { UNWIND [2, 3, 1] AS nbr RETURN nbr ORDER BY nbr ASC }
$x = 1
$nbr = 3
:param [{nbr: x}, {nbr: y}, {nbr: z}] => { UNWIND [2, 3, 1] AS nbr RETURN nbr ORDER BY nbr ASC }
$x = 1
$y = 2
$z = 3
:param [{n: example}] => { MATCH (n) WHERE = "Example" RETURN n LIMIT 1}
$example = {"identity": 4, "labels": [], "properties": {"name": "Example"}}}

8.4. Clear parameters

You can clear all currently set parameters from Neo4j Browser by running:

:params {}

8.5. Set several paramters

You can set several parameters with the :params command, this also clears all currently set parameters.

Integers are set to float with this style.

Example 17. Set several parameters
:params {x: 1, y: 2.0, z: 'abc', d: null, e: true, f: false}
$x = 1.0
$y = 2.0
$z = "abc"
$d = null
$e = true
$f = false

8.6. Duration for the query parameters

Parameters are not saved when you close the browser. You can save a :params command as a favorite to quickly populate parameters again.

9. Browser URL parameters

Neo4j Browser supports some URL parameters defined in the query component. The query component is preceded by a question mark (?) and contains a query string that is a sequence of key–value pairs separated by an ampersand (&).

9.1. Connection frame

Pre-populate the connection frame with the connection URL and set the database.

The syntax is:

http://localhost:7474/browser?connectURL=[connectionURL]&db=[databaseName] Deprecated
Example 18. Connection URL and database

This pre-populates the connection frame with:

  • Connect URL: neo4j://localhost:7687

  • Database: neo4j123

  • Username: alice


9.2. Pre-populate the editor

Pre-populate the editor with a command when Neo4j Browser starts. Supported browser commands are:

  • guide

  • param

  • params

  • play

The :play and :guide commands run automatically.

The syntax is:

Example 19. Guide intro
:guide intro
Example 20. Play movies
:play movies
Example 21. Param
:param example=>1
Example 22. Params
:params {example:1,foo:"bar"}

10. HTTP REST requests

Neo4j Browser supports the following HTTP REST commands:

  • :delete — HTTP DELETE.

  • :get  — HTTP GET.

  • :head — HTTP HEAD.

  • :post — HTTP POST.

  • :put — HTTP PUT.

It is possible to use these commands to query the Neo4j HTTP API.

The Neo4j REST API was deprecated in Neo4j 3.5 and was removed from Neo4j 4.X versions.

Example 23. HTTP API
:get /
  "bolt_routing" : "neo4j://localhost:7687",
  "transaction" : "http://localhost:7474/db/{databaseName}/tx",
  "bolt_direct" : "bolt://localhost:7687",
  "neo4j_version" : "4.3.0",
  "neo4j_edition" : "enterprise"
Example 24. HTTP API — transaction
:post /db/neo4j/tx
{"results":[],"errors":[],"commit":"http://localhost:7474/db/neo4j/tx/2/commit","transaction":{"expires":"Fri, 20 Jan 2222 10:11:12 GMT"}}
Example 25. HTTP API — transaction and commit
:post /db/neo4j/tx/commit {
"statements": [
  "statement": "CREATE (n $props) RETURN n",
  "parameters": {
    "props": {
      "name": "My Node"
  "statement": "CREATE (n $props) RETURN n",
  "parameters": {
    "props": {
      "name": "Another Node"