Nextion Editor Guide

Parts to this document

  1. Overview
  2. Custom Settings
  3. Main Interface
  4. Nextion Components
  5. Debug Simulator Overview
  6. Uploading your Project to your Device
  7. External Tools


This document (the Editor Guide) will go through various features of the Nextion Editor. The Nextion Editor is used to rapidly create Human Machine Interface GUIs for Nextion HMI devices. As such the GUI can be created within Hours instead of Weeks, and Days instead of Months. So while we won’t be covering such basics as opening a file, we will point out somethings that might prove helpful to know, and make reminders where they need to be made.

Nextion HMI devices are 5.0V TTL Serial devices, with each model providing their stated recommended power supply requirements (ie. 5.0V 1.0A) listed in the model specific Nextion Datasheet.  As the power supply is the heart of every project, it is wise to provide your project with a quality heart.  The chosen power supply must provide clean, stable and reliable power at the recommended voltage and current, failing to do so may result in damage to your Nextion device through overvoltage, undervoltage or undercurrent.

Nextion communications by default use an uncomplicated TTL Serial: None parity, 1 Start bit, 8 Data bits, 1 Stop bit, idle HIGH. As such, Nextion can be used with any one of over 68,000 microcontrollers that either has: a Hardware UART, or two digital IO pins to bit-bang a software serial. Optional Instruction CRC has been added since v0.58, but is not a requirement.  Additionally, the optional advanced Protocol Reparse Mode (since v0.53), provides users an ability to override Nextion’s default Serial handling and write their own project specific Nextion side Serial handling, is not required for a successful project.

Nextion Editor easily creates touch driven GUIs: from the simple interfaces where the component Send Component ID checkboxes notify the user’s microcontroller of touch event occurrences, to the much more complex interfaces where users customize through adding their own Nextion Instruction code to timer, touch and other Nextion side events.  As Nextion is a very capable device and can achieve some pretty amazing results, it still remains that the Nextion device is not meant as an MCU replacement and good design would say the user’s chosen MCU should remain in control of the project.

The Editor Guide will refer exclusively to the new and current versions of the Nextion Editor and not the LTS Edition. At the time of writing this guide, the current version is 1.61.2.  Where an item within the guide may be specific to a particular Nextion series, the following icons may be used to represent the series:
Basic T: ,  Enhanced K: , and Intelligent P .  Where an item may apply to a combination of series: both Basic and Enhanced:  ,  both Enhanced and Intelligent: , or the item applies to All series: .


  • Windows Operating System (Windows 10 is current, minimally XP or later). Users must know and be able to use their Windows OS. Windows support is beyond the scope of Nextion (especially after End-of-Life).
  • .NET 3.5 Assemblies installed. When needed, download and install the .NET 3.5 Assembles from the Microsoft Website [here].  Do not confuse having a newer Assembly (such as 4.0, but no 3.5) as somehow replacing the need to also have the correct 3.5 Assembly.  Finally, your system may have many such .NET Assemblies.
  • Ensuring Microsoft Visual C++ 2015 Redistributable Update 3 is installed and up-to-date [found here] resolved a rare issue for a few users.  Do not confuse having a newer package (such as 2019, but no 2015) as somehow replacing the need to also have the correct 2015 package.  Finally, your system will have many such VC++  Redistributable packages.
  • A reasonable sized monitor for the model’s resolution you are designing for is only good sense. When designing for a 320×240 or 240×320 model then a standard monitor size is probably sufficient. However, if one is designing for 1024×600 or 600×1024 resolutions, then it would stand to good reason not to expect best ease from using an 800×600 monitor resolution. For comfort, then it is senseful to use a large enough monitor so that your design canvas, tool panes, menus, and event panes fit for your designing comfort. It is not appropriate to blame the Editor software for your too small monitor when you really know you needed more screen real estate.
  • Basic programming skills are prerequisite. The Nextion Instruction Set is made up of ASCII text based commands inbound, and significant first byte binary Return Data. A component’s Touch Event “Send Component ID” can easily be used to defer programming tasks to the user’s MCU.  As such, quickly creating an HMI GUI for Nextion does not demand extreme skills – but basic programming skill are expected. When programming logic Nextion side, then users should have a foundation in programming.
  • Legacy Nextion devices require a firmware upgrade before using LTS Edition or newer Nextion Editor firmware or risk bricking the device. (see detailed notes in Legacy Devices section).
  • Uploading your completed Nextion HMI project can be accomplished either by microSD card or over TTL Serial. Note: Not all microSD cards are designed with embedded in mind (such as the newer ultra high speed camera cards), instead try an HC Class 10 microSD card.  When uploading over Serial, it is common to use a USB to TTL Serial adapter.  While there are so many, if needing a reliable adapter then Nextion sells the FocaMax.  Ultimately, there are dozens of manufacturers for each of these, it is the user’s domain and duty to know their device installation, configuration and operation.
  • Nextion can be used with one of over 68,000 MCUs: any MCU with an internal UART module or two digital pins to bit-bang a Software Serial. MCUs can be programmed in one of over 130 programing languages. Users MCU side programming is beyond the scope of Nextion and remains the user’s domain and duty to know and understand their chosen MCU, their chosen programming language, their chosen Compiler and libraries used.

Note: Editor installations on other Operating Systems have been accomplished successfully, but is not officially supported and beyond scope of any manual.

An important note on using legacy Nextion devices:

Every Nextion device was factory tested to work with the Nextion Editor version that was current at the time the Nextion the Nextion device was made.  This is to say a Nextion device purchased April 2016 would work with the Nextion Editor version v0.33 (current version at that time).  For very old Nextion devices with with project firmware v0.32 and before, these Legacy Nextion devices require upgrading their firmware to an intermediary level firmware (v0.38 to v0.53) before uploading an LTS Edition or newer Editor TFT file to the Nextion device.  Those users with legacy Nextion devices having v0.32 or prior firmware that jump straight into an LTS or higher version TFT firmware can risk bricking their legacy Nextion devices.

Legacy Nextion devices are limited to the Basic series devices (mostly from the original campaign) with Nextion TFT firmware v0.32 or prior. This means Basic series Nextion devices from around May 2016 and forward are likely not legacy. Any of the Enhanced or Intelligent series Nextion devices are not legacy and remain unaffected.

Which Nextion devices are classed as Legacy and require intermediary upgrade:
– your device is a T Series Basic model NX----T---_011 (blue PCB)
– your device has the Itead logo and not the Nextion logo
– your device was never used with Nextion Editor v0.38 or later
– your device connect reports firmware below S62 (v0.38)
– device now triggers a Device Null error (was legacy, see LegacyFix below)

Note: Once version v0.38 is used, an earlier version can not be used.

Users with legacy Nextion devices can upload a v0.42 Intermediary TFT file [found here] to their device to satisfy this intermediary step and proceed with confidence to use Nextion Editor LTS Edition or newer Nextion Editors without this issue.  Users that bypassed this warning and bricked their Legacy Nextion device can try without guarantee to reanimate their bricked Nextion using the LegacyFix TFT file. LegacyFix is specific to this issue and does not fix any other issues, it will not repair electronics and bring dead devices to life.

Downloading the latest Nextion Editor

For new project development, the latest version of the Nextion Editor is recommended and can be downloaded [from here]. At the time of writing this guide, the current version is 1.61.2.

There are two versions of the nextion-setup-v1-61-2 available for download.

  • The EXE version is installed through the Windows MSI for a more automated installation. Only one version of the Nextion Editor may be registered at a time via the EXE version. When updating within the Nextion Editor, Auto Update will install the EXE version
  • The ZIP version can be unzipped into a user chosen folder and run directly from that folder. For maintaining multiple versions of the Nextion Editor, the ZIP version is recommended. When updating within the Nextion Editor, Manual Update will launch your web browser to the download page so you may download the ZIP version

Downloading Nextion Editor LTS Edition

A special LTS Edition of the Nextion Editor, so named for Long Term Support, is available for maintaining older projects (HMI created with version v0.53 and prior) where code compatibility is required (LTS is based on v0.53 but is not v0.53).  Where the version of Nextion Editor that the HMI was created with is available, nothing prohibits the user from continuing to develop using the HMI’s original version without upgrading to the LTS Edition. There are no updates (now or in the future) for the LTS Edition.  For new project development, it is better to chose the newer 1.61.2 Nextion Editor version over the LTS Edition.

  • The Nextion Editor LTS Edition is available only as a ZIP version and will lack all the bells and whistles of the newer versions. To install, simply download and unzip into a chosen folder and then run the Nextion Editor directly from that folder.

1.1 Styles

The Nextion Editor can be set to a Blue or Black themed style. (Style is found in the upper right corner).

1.2 Panes

Many of the panes can be adjusted on both size and their location. To resize, drag the splitter between panes and move to resize the panes. To move a pane to a more convenient location, drag the title of the pane and release on your preferred drop point. Panes can also be pinned to retain a fixed position or unpinned to collapse to an edge when not in focus. When needed, you can reset these settings by selecting the Reset layout under the Setting menu.

1.3 Other Editor Settings

Other settings in the Nextion Editor can be configured in Configuration under the Settings menu. The default font of the Nextion Editor can now be changed to suit your taste. The default timeout of 100ms for the Debug Simulator can be adjusted from 20ms to 5000ms. Code hints, highlighting, description, tooltips and auto-complete can be set individually for the Editor and the Debug Simulator. Default path for eeprom and sd files can be customized to suit your taste. When needed, you can reset these settings by selecting the Reset layout under the Settings menu.

1.4 Recent Projects

In the Display Tab of the Nextion Editor on starting the Editor, there is a section listing the most Recent Projects. The number of recent projects tracked is by default 10, and can be increased. Right-clicking a project allows you to select from the following:

* Open the file: if the project file exists, then opens in the Editor
* Open the folder: if the folder exists, then opens the folder in Explorer
* Delete the current records: clears the highlighted recent projects from the list
* Delete the invalid records: clears non existent projects from the list
* Delete all the records: clears the recent projects list
* The number of recent project setting: allows you to adjust the number of projects tracked

Nextion Editor Main Interface


  1. Title Bar
  2. Main Menu
  3. Toolbars
  4. Page Pane
  5. Toolbox Pane
  6. Attributes Pane
  7. Picture Resource Pane
  8. Font Resource Pane
  9. Audio Resource Pane
  1. Gmov Resource Pane
  2. Video Resource Pane
  3. Design Canvas (Visual Components)
  4. Non Visual Components
  5. User Event Code
  6. Output Pane
  7. Display/Program.s
  8. Status Bar
  9. Keyboard Shortcuts

Title Bar

The Title Bar contains the path and filename of the HMI project file when an HMI project is loaded.

When an HMI project is not currently loaded a TFT file can be

  • loaded into the Debug Simulator by pressing the toolbar Debug
  • uploaded to the Nextion device by pressing the toolbar Upload

Main Menu

File Menu

Here, Users can create and save a New project, Open an existing project, Save the changes made to the current project, save the current project with a new name with Save AsClose the current project, and Exit the Nextion Editor. Import Project will append an existing project into the current project – usually with resulting naming and renumbering issues. As such, it is recommended to export pages individually and then import the individual pages if and as required. The Clear Recent Projects item to clear the Project filenames from the Recent Projects pane (without deleting any of the project files from the hard drive) has been removed from new Editor versions in favour of having this and more options right from the Recent Projects pane with context click.

The Version backup folder menu item opens the C:\Users\Username\AppData\Roaming\Nextion Editor\backup folder.  When an HMI file is opened that was created in an older version of the Nextion Editor, a copy of the original HMI file is saved with version in the filename to this folder, and then the old formatted HMI file is converted to the new HMI format of the current version Nextion Editor and saved with the original name.  This is useful to know in the event that a conversion may have compatibility issues and the original-before-conversion copy of your HMI may be desired.  Such is not a replacement of a real system backup when you are coding and developing a product.

The now missing Open Build Folder menu item previously C:\Users\Username\AppData\Roaming\Nextion Editor\bianyi has been replaced with the more favourable TFT file output to give the users more flexibility on where the generated TFT file should be placed. By default, the new folder would be C:\Users\Username\AppData\Roaming\Nextion Editor\work\a-xxxxxxxxxxxxxx\output and the user can now chose their destination folder, such as directly to their microSD card saving steps previously needed.

The Virtual EEPROM Folder contains the eeprom.bin file used by the Debug Simulator for the Enhanced and Intelligent series models. By default the Virtual EEPROM Folder is located at C:\Users\Username\AppData\Roaming\Nextion Editor\eeprom\.

The Virtual SD Card Folder is used by the Debug Simulator for the Intelligent series and allows users to put copies of their microSD card project files in this folder for testing. By default the Virtual SD Card Folder is located at C:\Users\Username\AppData\Roaming\Nextion Editor\sdcard0\.

Both of these Virtual Folder locations can be customized in the Configuration menuitem of the Settings Menu.

Tool Menu

Under the Tools menu, users can access the extra tools Font Generator, GmovMaker, VideoBox and PictureBox. These are covered individually in Section 4 of this Guide.

Setting Menu

The Setting menu contains two items: Configuration and Reset layout.

In the Configuration menuitem, the user can choose for the Nextion Editor and the Debug Simulator if code should be highlighted or not, if Auto-Complete should be on, if the descriptions for instruction parameters should be on or not, if the tooltips should be shown when the mouse is over the toolbar buttons.

For serial data in the Debug Simulator, the timeout can be adjusted from its 100ms default value to a user selected value within the range from 20ms to 5 seconds.

For the new Intelligent Series, the user can choose if there should be a 3 second delay at screen edge before allowing the component position to escape to the outside of the canvas area. This is useful to be on, especially in the Basic and Enhanced models as out of bounds positioning is not permitted and will cause the project to not compile.

For the virtual eeprom/sdcard folders, the user can choose to use the default path, or can set their own custom path that is more suited to their system and workflow.

Transparent color replacement value allows a user to enter a 565 color value for when transparent color is disabled that transparent pixels will use this value.  By default this value is 65535, the 565 color value of white.

The default Font used for the Nextion Editor can be changed to suit the users taste. Resetting the font to the default Microsoft Sans Serif will return the Editor to its normal traditionally used font.

Finally, the image format can be set to make use of YUV420 or YUV422 formatting.

Reset layout menuitem will reset the Nextion Editor default panes back to their original default positions. This is a useful starting point if you have somehow misplaced your pane or positioned it in some obscure unreachable position.

Help Menu

The Nextion Instruction Set is no longer available as a Tab in the Nextion Editor.
Selecting Instruction Set menuitem will launch the Nextion Instruction Set in your default web browser.
Selecting Editor Guide menuitem will launch the Editor Guide in your default web browser.

About Menu

Selecting About Nextion Editor menuitem in the About menu will show the about box with the version of the Nextion Editor. Clicking the link will take you to the Nextion website where you can access the forums and other documentation.

Selecting Check for new version menuitem in the About Menu will show the Update dialog when a new version is available (see Downloading the Nextion Editor at the beginning of this Guide), or a dialog informing that you have the most recent version.


Open, New and Save

These will Open an existing project, create a New project, or Save the current project.


Use Compile to check for errors in the currently loaded project. Any Warnings or Error Messages will be placed in Output Pane.

Pay attention to any warnings as these will mean your project may not run as you expect.  Pay attention to any error messages as they will need to be corrected before continuing. Error messages are descriptive, and if it is a code error then the user can jump directly to the coding error location.

Compile is more of a building and assembly process.  This is only stated so that users do not make the wrong expectations of native machine code when making Feature Requests and Bug Reports.  Nextion remains closed source.

A TFT file is no longer built and placed in the bianyi folder on Compile.  To generate a TFT file, one has to use the TFT file output menuitem located under the File Menu.


The Nextion Editor contains a built-in Simulator that can be accessed via the toolbar Debug. To be clear this is not a precision emulator and is intended to be sufficient to assist in debugging a users project. It in no way is meant to replicate the Nextion device exactly. (Any Windows OS is sufficient to make such precision unattainable.) This will be covered in a future section.

If a project is not currently loaded in the Nextion Editor, Debug will open a dialog to open a compiled *.TFT file directly. This is handy for loading demos or sharing ideas without surrendering your original source code. Although the Debug Simulator can run a *.TFT file from any Nextion series or model, it is important to note that the same version used to create the *.TFT file is required to simulate the *.TFT file.  (ie: an older v0.36 project TFT file can not be simulated with the newer current version of the Nextion Editor.)


Selecting Upload will launch the Upload to Nextion device dialog. Ensure the Nextion is connected via serial (typically via USB to TTL adapter) before upload or the Port may not be available to select. Auto search feature will look for your Nextion’s reply to the connect command, but realize that data is being sent on all serial ports that are searched (and may interfere with the other connected serial devices). A better choice is to select the correct Port and Baud Rate. Proper configuration of Serial adapters, Windows drivers, device conflicts, etc is beyond the scope of Nextion support and the domain of user responsibility to know their used Operating System and device operation.

Once Nextion has responded to the connect command, the upload process will begin. Do not interrupt this process until completed. If the process has been interrupted, resetting the serial port may be required. When a partial *.TFT file has been uploaded and uploading over serial is no longer an option, then the user will need to upload via the microSD method.  Refer to Section 5 of this guide.

Copy, Cut, Paste and Delete

Users can select components or multiple components and then Copy, Cut, Paste or Delete as required.  Paste contains a drop down option to In place paste which will copy without any vertical or horizontal offsets.

Lock and Unlock

Users can select components or multiple components and then Lock or Unlock as required. Locking prevents a component from being repositioned with the mouse until unlocked. A lock icon appears in the upper right corner of the visual components when locked that can interfere with visual inspection of your HMI design.

Undo, Redo

Use Undo and Redo to Undo the last operation, or to Redo the last operation undone.

The Component Layout Toolbar

For Renumbering components: Bring Top (Arrow Up) will take the selected component(s) and renumber to the highest .id on the page. Bring Bottom (Arrow Down) will take the selected component(s) and renumber to the lowest (starting at 1, page component is always 0) .id on the page.

For Aligning components: Align Left, Align Right, Align Top and Align Bottom will take a group of selected components (green ID labels) and bring the alignment to match the component with the blue ID label.

For Resizing components: Same Width, Same Height and Same Size will take a group of selected components (green ID labels) and set the size (width, height or both) to match the component with the blue ID label.

For Spacing components: make Horizontal spacing equal, Increase horizontal spacing, and Decrease horizontal spacing will take a group of selected components (green ID labels) and adjust the horizontal spacing between components using the component with the blue ID label as the baseline component. Likewise: make Vertical spacing equal, Increase vertical spacing, and Decrease vertical spacing will take a group of selected components (green ID labels) and adjust the vertical spacing between components using the component with the blue ID label as the baseline component.


The steps to configure your HMI project for your Nextion Series and Model is usually done at the time of creating a New project. When you need to make changes, Device will launch the following window with the Device tab selected. First select the Nextion Series: Basic for the T models, Enhanced for the K models, and Intelligent for the P models. Then select your Nextion Model. For the multi-touch capacitive Nextion models: Select the Nextion Model closest matching, multi-touch will be handled by Nextion when capable without further user interaction.  Note: Capacitive models are factory calibrated, as such touch_j calibration is only for Resistive models.

Selecting the DISPLAY tab, the user can select the orientation and the Character Encoding. 0° is the native viewing angle for the selected model. Users can choose alternative orientations (90°, 180° or 270°) but this will not be the native viewing angle. Character Encoding is default iso-8859-1. Select from the character encodings that make sense for your HMI project to best display your local character sets. There are a selection of single byte and double byte character sets available. Unicode will not be among the supported encodings.

Currently supported Character encodings include:
ASCII, ISO-8859 (1,2,3,4,5,6,7,8,9,11,13,15),
GB2312, BIG5, KS_C_5601_1987, SHIFT-JIS, KOI8-R,
Windows 874, 1255, 1256, 1257, and 1258, and UTF-8.

Note: An encoding is a character mapping of value to character. Computer systems and MCUs use numeric values and not characters. A byte numeric value 0x41 in single byte ASCII encoding will reference the character A. Your MCU will not send A, it sends byte 0x41 (which in many cases maybe mapped to the letter A), but does not explicitly mean 0x41 renders A in every encoding. A Byte value of 0xC4 can map to different characters in different encodings, or even be undefined (mapping to no character). While modern computers can do translations between many encodings, your MCU will likely not. It is useful to research the encoding you are planning to use.

If you desire to password protect your entire HMI project, selecting the Project tab will bring up the Open Password Setting button. If an existing password exists, it will need be entered before a new password can be set. When a Password is lost, it is not retrievable. Fair warning is given: DO NOT LOSE YOUR PASSWORD. There is no recovery! A project with a lost password would need to be rebuilt – So, do not lose – or do not use.

Two additional options exist on this page.  The first is the One-time update, useful when you upload via microSD to a single Nextion device and will reuse the microSD card and want to skip the steps of removing the *.TFT file after update (there can only be 1 *.TFT file on the microSD card for updating via microSD).  The other option is for the Intelligent Series Memory file storage.  Space needs to be set aside for using ram/ file paths, specify the amount of space in Bytes here.


Selecting ID to will toggle if the component .objnames are displayed in the upper left region of the component space. Yellow labelled components have a .vscope local, while black labelled components have a .vscope of global. (Hint: Event code is never global). When selecting multiple components, green labelled components indicate multiple components have been selected, while the one blue labelled component will be used as the baseline component. To change the baseline component while the group is still active, simply click on the already selected component you want to become the baseline component.

Canvas Zoom

New to the Nextion Editor is the ability to Zoom the design canvas both in and out. Users can zoom from 20% to 600% using the slider, or increment steps using the + and – buttons on the ends of the slider. The value of the zoom is shown in percentage to the right of the Canvas Zoom. Clicking on the percentage zoomed allows you to reset the zoom back to an unzoomed 100% state.

Project Startup Code

Selecting the C on the toolbar will open the Program.s tab in the Design Canvas area. To return to the Design Canvas, click the Display Tab. The Project Start Up code section is a newly introduced concept allowing for users to define and initialize additional int globals (such as sys0=0). At the moment only int 32 bit signed integers are supported. Additionally project start up code can be added in this section to be run before the HMI runs using Nextion Instructions.

Remark Line On / Remark Line Off

When in the Project Startup Code, using the Comment or Uncomment on the tool bar will comment the selected line(s) or uncomment the selected line(s) in the same manner as the Event Pane does with user code.

Page Pane

Every HMI project needs to have at least one Page. Pages are created or imported into your HMI project through the Page Pane. A Page is created with Add, deleted with Delete, and copied with Copy. Insert will create a new page before the highlighted page. Use the Arrow Up and Arrow Down to renumber the page index number within the Page Pane. Using Delete all (Trash) will delete all pages within the project.

Pages can be renamed to a maximum of 14 characters and the page names are case sensitive (avoid using space and other characters that can be code ambiguous as this could cause code parsing issues: Since the Intelligent Series, the Editor compile becomes more strict). To rename your page highlight the page, right click. and select Rename. Then enter your new name (it is recommended to press Enter to ensure the change takes place). Double clicking a Highlighted page name will also trigger the page renaming function.

The page Lock and Unlock functions are only accessed by right clicking the highlighted page name and selecting Lock or Unlock. If the page has been locked with a password, the password must be entered to access the components and event code. There is no password recovery should the password becomes lost, so don’t use or don’t use. As an example, the keyboard pages are imported as locked, but do not use passwords (the keyboard pages are also a good coding example to review). When keyboard pages are imported by the Nextion Editor component .key attribute, reset system page option is included in the context menu, which is used to reload the keyboard page and proper orientation in the cases where the keyboard page may have been edited or display orientation options may have changed.

Pages can be exported from one project to another project with Export page. This is the preferred way to share components and partial projects. Page files *.page can not be compiled on their own. If you want to export a page as locked or locked with a password, this must done before exporting.

To import a page, use Import page. Imported pages can be used independent if they are locked with a password, locked without a password, or unlocked. Locking is to protect the code. So as long as proper documentation about the page variables and functions accompanies the *.page file, an end user can use even a locked page. When a page is imported with naming conflicts, the affected conflicting names will be renamed. It is therefore relevant to perhaps select meaningful names. To import a copy of one of the keyboard pages, one can either import the *.page file directly or use the .key attribute of a Text, Scrolling Text, Xfloat or Number component.

In an HMI project a page is a localized unit. When changing pages, the existing page is removed from memory and the requested page is then loaded into memory. As such components with a variable scope of local are only accessible while the page they are in is currently loaded. Components within a page that have a variable scope of global are accessible by prefixing the page name to the global component .objname.

As an Example: A global Number component n0 on page1 is accessed by page1.n0. A local Number component n0 when on page1 can be accessed by page1.n0 or n0, but there is little sense to try access a local component if the page is not loaded. Only the component attributes of a global component are kept in memory. Event code is never global in nature.

A Page always contains a page component, and this page component will always have an .id of 0. Making the page component global, does not make the components within a Page global – just the very few page attributes of the page component. On a Basic or Enhanced model: of which only .pic or .bco are changeable at runtime, Intelligent models: additionally, the page swipe pages and effect. The page component .id used with the b[.id] component array is not the page index number used with the p[index] page array.

A Page component can have a background of either : Solid color, image background, or no background. An image background should use a fill screen image to avoid calling non-existent data. No background will show the current page components over top the last unloaded page, this must be used with caution. No background on a no background, on a no background soon causes unwanted side effects. There is a hard limit of 250 components allowed per page, and theoretically up to 254 pages per project (highly likely resources will be depleted before any page253 is reached).

Toolbox Pane

The page component not listed above is always created when the new Page is added to the Page pane. When creating a new project HMI, the first page named page0 is already added to the  project. The page components will always have an .id of 0 and is always the bottommost layer. New page effects and swipe-to-change-page capabilities are added for the Intelligent series.  There is a hard limit of 250 components allowed per page.

Many components have multiple .sta choices of
– crop image (pulls background from .x and .y location of a user chosen picture resource)
– solid color (sets background to be a user chosen 565 color)
– image (text if any will be drawn over the user chosen image)
– transparency: Intelligent only (pulls background from underlying layers)

Many components have multiple .style choices of
– flat (no lines will be added around edges)
– border (lines will be drawn around edges)
– 3D_Down (lines will be drawn to yield impression of lowered)
– 3D_Up (lines will be drawn to yield impression of raised)
– 3D_Auto (lines will be drawn Up/Down according to state)

Many components have multiple text alignment and placement options
– .xcen of Left, Center or Right
– .ycen of Top, Center or Bottom
– .spax will add extra blank pixel spacing to right of each character
– .spay will add extra blank pixel spacing to bottom of each character
– .isbr for multi-lined (set to true) or single line (set to false)
– .pw for masking (Character is off, Password will mask with asterisk)

For the Intelligent Series, most components have new capabilities
– repositionable by assigning .x and .y values
– user dragable at runtime by setting .drag
– fading by setting .aph
– various effects found in the .effect attribute
– additional component attributes exclusive to Intelligent models.

Note: with many more customizable attributes for the Intelligent Series components, it is wise to click the attribute in the Attribute Pane (see Section 2.6) for a full attribute description. ie: Intelligent Series Gauge .vvs2 attribute now controls the foot length of the gauge needle (attribute not available for the Basic or Enhanced Series).

The Text component is a highly customizable component. The Text component has the .pw attribute for masking (Character is off, Password will mask with asterisk) and the .key attribute for integrating one of the included example keyboards (must be set to .vscope global before use).

The Scrolling text component combines an integrated timer component with a text component. The .pw option is not available with this component. The .key attribute allows for integrating one of the included example keyboards (must be set to .vscope global before use). There is a hard limit of 12 timer components per page within your project.

The Number component is used for signed 32-bit integer values. The .lenth (as spelled) sets the number of digits shown (useful for leading zeros). The new .format attribute allows for a choice of integer, currency (comma separated every three digits, not floats), or hexadecimal. Input should be in integer or hexadecimal. The .key attribute allows for integrating one of the included example keyboards (must be set to .vscope global before use).

The Xfloat component is used for signed 32-bit integer values. The .vvs0 sets the number of digits shown to the left of the decimal (useful for leading zeros). The .vvs1 sets the number of digits shown to the right of the decimal. The .key attribute allows for integrating one of the included example keyboards (must be set to .vscope global before use).

The Button component is again highly customizable and integrates text in a momentary manner. Use text, images or event code to suit tastes.

The Progress bar component is for progress, thus a valid range of 0 to 100 to represent the percentage of progress. (Please no more requests to extend the range, even if many may give 110% effort). Best effects for progress are attained using images.

The Picture component will allow any picture resource to display in the Picture component. Example p0.pic=3. It is important that the picture resource is the user defined size in .w and .h or the picture resource will over draw the picture component boundaries, or incorrectly insert adjoining data. The Picture component is useful to represent multi-states and animation sequences.

The Crop component will replace its boundaries with the same location and boundaries from the picture resource pointed to with .picc. It is highly recommended that the picture resource being used is a full screen image to avoid errors (must be fullscreen image). The Crop component can be useful to represent states.

The Hotspot component is a user defined touch spot to its overlaying region. At a 2 pixel by 2 pixel region, it makes for a useful code holder to be later called by the click command – thereby creating a user defined function. As a Hotspot, it turns any image area into a button, such as in creating a customized keyboard.

The Gauge component is a full circular component with value in degrees. This means a range of 0 to 360. Gauge components are not useful for stacking (example: a three handed clock), as the redrawn gauge will overwrite any lower gauge. In Basic and Enhanced series: Gauge components are not useful for stacking (example: a three handed clock), as the redrawn gauge will overwrite any lower gauge. The gauge component is always a square in nature. Semi-circular gauges at the screen’s edge are not achieved with the gauge component. In the Intelligent series: a stackable gauge with highly customizable needles and out of bounds positioning can achieve many effects not possible in the previous series.

The Waveform component is used to plot y axis data points on up to 4 channels. Waveforms are never global: in that adding datapoints with add/addt can only be done when waveform is on the active current page. Waveform .vscope of global allows plotted data to be maintained between page changes. Waveform .vscope of local, the data points are not retained, changing pages away and back will revert the waveform to an emptied state. Up to 5 waveforms can be used on a single page. The Waveform component is limited to a y axis data range of 0 to 255 or 0 to waveform height -1. As a data point is added, it will consume one column, with the next data point using the next column. Recent changes now allow a variable to be used in the add command. Example add 1,0,h0.val. The addt command becomes useful to refill the waveforms on page load (such coding remains within the user domain).

The Slider component can be horizontal or vertical. The slider has the added event code for Touch Move, useful for providing updates to the sliders current position. Best results are attained with images. Slider length includes the size of the thumb as well as the range (often overlooked in calculations).

The Timer component is not expected to be a high precision interrupt driven component. It is however useful for queueing reoccurring event code after elapsed .tim has expired. As code is sequentially processed, it is very easy for the time to process the requested user event code to exceed the .tim intervals and therefore not interrupt driven (to avoid such stack overflows) is then not high precision. There is a hard limit on the maximum number of timers running in a single page, this limit is 12. Beware that the scrolling text component integrates 1 timer. Timer attributes can have a variable scope of global, event code is never global. As such timer code can only be triggered within the current page they are designed in. As the timer is a non visual component, they are added below the Design Canvas.

The Variable component is a non visual component and also added below the Design Canvas. Variables are either 32 bit signed numeric or string content.

The Dual-state button component is an expanded Button maintaining its state between toggles.

The Checkbox component is another example of a lightweight dual-state component with less customization and lower memory usage.

The Radio component is yet another example of a lightweight dual-state component with little customization and lower memory usage. Obtaining grouping is achieved via user code (remains in the user domain).

The QR Code component is used to generate a 2D scanable QR. It is limited to a byte maximum for the .txt_maxl attribute of 84 (of up to a max 154 bytes) on Basic T models and 192 bytes on the Enhanced K and Intelligent P models.

New components for the Intelligent series

The Switch component is an expanded dual-state combining text and graphics.

The ComboBox component is used to present an expandable/collapsible selectable list with the .path attribute holding options one per line. The number of selected item held in .val and .txt holding the text of the selected item.

The TextSelect component is used to present a cyclic spinner with .path attribute holding options one per line. The selected item number in .val and .txt holding the read-only text of the selected item.

The SLText component is used to present a scrollable textbox with .txt holding multiline data. The position of the list in pixels can be set through the .val_y attribute.

The DataRecord component is used to present a dataset in a scrollable table. DataRecord supports up to 12 fields per record. DataRecord incorporates 4 methods .insert(), .delete(), .up() and .clear(). Configuring DataRecord attributes for your application requirements will need be thoughtful at your HMI design time.

The FileBrowser component is used to present a folder and file structure tiled in a filter capable browser. The .dir attribute holds the folder path, and the .txt attribute holds the selected filename. FileBrowser incorporates an .up() method to return to previous folder. Be sure to ensure an appropriate font has been included to your project for filenames to be displayed.

The FileStream component is a non visual component for working with a file, it incorporates 5 methods .open(), .close(), .read(), .write() and .find().

The Gmov component is used to present an animation, with up to 16 Gmov components on an HMI page. Use the GMovMaker Tool to create an animation in the Nextion *.gmov format using supported *.jpg, *.bmp, *.png and *.gif source files. The Gmov component contains an additional Play completed Event to trigger user code at the end of each iteration of the animation.

The Video component is used to present a movie, with up to 6 Video components on an HMI page. Use the VideoBox Tool to convert a movie into the Nextion *.video format. The Video component contains an additional Play completed Event to trigger user code at the end of each iteration of the Video. Use the .from attribute as external file and .path attribute to use *.video files stored in ram or on Nextion’s microSD card.

The Audio component is used to present pictures that are stored in ram or microSD card. Use the VideoBox Tool Audio tab to create audio resources in the Nextion *.wav format. The Audio component contains an additional Play completed Event to trigger user code at the end of each iteration of the Audio. Use the .from attribute as external file and .path attribute to use *.video files stored in ram or on Nextion’s microSD card.

The ExPicture component is used to present pictures that are stored in ram or microSD card. Use the PictureBox Tool to create picture resources in the Nextion *.xi format that can be stored in ram or on Nextion’s microSD card.

To add any of the above components to the currently design page, simply click on the component and it will be added with its .id set to the number of components on the page. All components within a page are listed in .id ascending order in the Component Drop down in the Attributes Pane. Then continue with placement and adjustment of .attributes as desired.

Attributes Pane

The Attribute Pane contains the list of components included within the current design page in the Component drop down. Clicking on a component, or selecting it from the drop down will display the component’s available attributes. The left side contains the attribute name, the right side contains the attributes current value. Clicking on an attribute will display the attributes meaning and valid range/options at the bottom of the Attribute Pane. Double clicking a field with bring up resource editor for the attribute if attribute has such (ie: .pco opens color picker, .pic opens picture chooser).

Any attribute in black is read only at runtime (with the exception of .objname and .key) The .objname and the .key attributes are inaccessible, and do not report. Any attribute in green can be both read and changed by user code at runtime. Empty unassigned attributes values or invalid attribute values will need to be resolved before a successful compile can be achieved. When renaming a Components .objname: avoid using space and other characters that can be code ambiguous as this could cause code parsing issues.

Page name prefixing is suggested to access a global component’s attributes on another page.
– example: page0.va0.val
Page name prefixing is not required to access a local component’s attribute on the current page
– example: va0.val

Note: Accessing a local non-page-prefixed name from MCU side code will address the version of the component present on the currently loaded page.  If pages page0,page1,and page3 each have a v0.val and page2 does not, then code calling va0.val when Nextion’s currently loaded page is page1 will update page1.va0.val and not page0.va0.val or page3.va0.val.  Likewise, when Nextion’s currently loaded page is page2 where no va0.val exists, such access/assignments will fail.

Attributes that have ranges are evaluated in full during Nextion’s parsing of a complex expression and as such care is required. Nextion is stated as simplex expression, although these rules are often bent. Use care.
– example: gauge z0 with a .val range of 0 to 360.
Should va0.val+step.val exceed 360 the assignment fails before arriving at modulo 360.
– this is the nature of simplex expressions (think assembly language), and bending the rules has side effects.

The various combinations of attribute choices provides a wide range of expected behaviours with too many combinations to cover in any manual(s). This combined with the Nextion Instruction Set creates the opportunity for very powerful HMIs.

There is a hard limit for a combined tally of attributes and user code of 65534.

Picture Resource Pane

Pictures are imported into your HMI project through the Picture Resource Pane. A picture is added with Add, deleted with Delete, and swapped with Replace. Insert will add the imported pictures before the highlighted picture. Use the Arrow Up and Arrow Down to renumber the picture resource number within the Picture Resource Pane. Using Trash will delete all pictures within the project. Note that Delete will not delete a picture resource if it is being used with a component.

The accepted picture types to import are *.jpg, *.png, non animated *.gif and *.bmp files. When importing a picture, the picture is converted into the 565 16 bit color format used by Nextion. In Basic and Enhanced models: Nextion is not a graphics card, as such transparency and in picture animation is not supported. In native 16-bit color, picture resources consume 16 bits per pixel, or width x height x 2 bytes. In Intelligent models: Nextion now supports transparency and image compression allowing more picture resources for the same space, the 2 bytes per pixel formula does not apply.

Exporting a picture resource is accessed by highlighting a the picture resource, right clicking and selecting Export. The available picture formats for export are *.jpg, *.png and *.bmp as per the resource being exported. Note that *.jpg may save space but is a lossy format: once the data is lost, it is lost. Note that exporting pictures is with the naming convention picture resource #.format. Exporting will overwrite a pre-existing file.

When using cropping, a full screen image is strongly recommended for the background. This avoids pulling data from non-existent space – which will resemble randomized colors (data from other locations). Cropping can consume more cycles than using a picture, using a picture will consume more cycles than solid colors. When cycle time becomes too high to render, tearing and flickering will be the sign. Nextion is an HMI device and not designed for HD multi-media and streaming. That said, amazing effects can still be achieved with purposeful programming.

A picture resource has the following limitations:
1) longest edge can not exceed 4080 pixels
2) width x height can not exceed 614400 pixels

Assignment of the picture by code at runtime would look like:
p0.pic=1ÿÿÿ over serial, or as p0.pic=1 inside an event as code.

Font Resource Pane

The ZI Font Resource is very important! If any visual component used in the user’s project contains a .txt or .val attribute, then at least one font must exist in the project. If a user wants to use various sizes of styled fonts in their HMI project, they will need to generate a ZI Font file for each style and size they will use. For most users this will mean starting with a ZI Font generated with the built-in Font Creator (covered in the Menu section above).

These *.zi font files will need to be added into the ZI Font Resource Pane. Each ZI Font Resource will show the font resource number, it’s given name user gave at creation time, it’s size in pixel Height, it’s character encoding, number of characters in the set and the size in bytes the font contributes to the HMI project’s overall filesize. The appropriate *.zi font can then be selected by its number and assigned in a visual components .font attribute. Note that the design size of the visual component is set at design time and can not be changed at runtime.

Assignment of the font by code at runtime would look like:
t0.font=1ÿÿÿ over serial, or as t0.font=1 inside an event as code.

Properly formed monospaced ZI font resources from v0.53 (and prior) will have a width that is either equal to the height or a width that is half the height. Height will always be a multiple of 8 from 16 to 192. ZI fonts are monobit (pixel is either on or off) and Fixed Width. Hint: Generating a proportional font like Arial where W and @ are 24×24 and squeezing into a 12×24 space is like pouring 2 litres into a one litre bottle and expecting all 2 litres have been saved. Fonts that do not conform to the ZI size formula just stated can indeed have issues when it is rendered on the Nextion device.

With the introduction of the Intelligent Series, an anti-aliased non-fixed width font can now be generated. Be mindful that the max visual space required for characters of an anti-aliased proportional font is not width x qty as it was with the elder ZI fixed width font. Proportional fonts such as Arial contain characters of varying width (W is indeed wider than l).

A ZI font resource can be viewed by selecting the font and double clicking the selected font. Subset ZI fonts can be redefined and regenerated with Change Font button at the bottom of the Font Preview window. Trash will Delete all loaded ZI Font Resources. Multiple *.zi fonts can be imported with Add. A font must not be associated to a component to remove with Delete. A font can be swapped out with a different font using Replace. Insert will import the font before the highlighted font. Use the Arrow Up and Arrow Down to renumber the font resource number within the ZI Font Resource Pane.

Exporting a font resource is accessed by highlighting a the font resource, right clicking and selecting Export. Note that exporting multiple fonts is with the naming convention font resource #.zi. Exporting will overwrite a pre-existing file.

Your Content Goes Here

Your Content Goes Here

Your Content Goes Here

Design Canvas Visual Components

This is the main design space for the visual/touch components for the current Page.  The Page’s page component is always .id 0 and always the most back layer.  The mouse coordinates are displayed on the Status Bar aiding in precision placement.  Selected components can be moved in one pixel offsets using the keyboard arrow keys.  For best precision, use the component’s .x and .y attributes.  Components selected with the left mouse click can be moved by dragging.  As such using the right mouse click to select a component will not accidently move the component.  Resizing a component via edge dragging can only be achieved on the bottom and right edges.  There is a limit of 250 components (visual and non visual) allowed per page.

Design Non Visual Components

A Page’s non visual components (Variables and Timers) will be listed in this area.  This area is not displayed if there are no Variable or Timer components used in the page.  There is a limit of 250 components (visual and non visual) allowed per page.

User Event Code

User Event Code can contain any valid Nextion Instruction. This section will not teach programming, but will quickly give an overview of the various types of Events where inserting user code is available. Event code is always local to page and never global.

Almost every component has the Touch Press and Touch Release events.
– The Touch Press Event includes a Send Component ID checkbox that when checked sends the 0x65 Return Data over serial on physical press. User code is run on either physical press or via the click command.
– The Touch Release Event includes a Send Component ID checkbox that when checked sends the 0x65 Return Data over serial on physical release. User code is run on either physical press or via the click command.
– The Send Component ID 0x65 Return Data over serial action can not be triggered by the click command. This is reserved for an end-user physical action received through the touch sensor. The click command will only trigger running the user event code.
– The Nextion Instruction printh command can simulate 0x65 Return Data (Actual or spoofed)

The page component contains both Touch Press and Touch Release as well as
– The Preinitialize Event user code is run before the loading of the HMI designed page.
– The Postinitalize Event user code is run after the loading of the HMI designed page.
Note: global values will persist, will local values return to their designed state.

The slider component contains b0th Touch Press and Touch Release as well as
– The Touch Move Event user code is run during drag of thumb when slider changes values.
– The Touch Move Event does not have a Send Component ID to avoid serial overflow.

The timer component only contains the Timer Event for user code.
– Refer to the Timer component in the Component Pane section for more details

Nextion Return Data is returned at the end of command execution
– it would otherwise not be wise to predict an outcome before the end.

There is a hard limit for a combined tally of attributes and user code of 65534.

Output Pane

The Output Pane contains details on the build process when Compile/Debug/Upload is selected. Compile needing to occur first, the user HMI is assembled into a usable TFT file for the selected Nextion Model. The first three lines of the output will list the total amount of global SRAM memory consumed by the HMI project, and then statistics for the total amount of Flash space the picture resources consumes, followed by the total amount of Flash space the ZI Font resources consumes.

The build process then goes through the project sequentially page by page. At the end of a successful page build, the page Memory stats are listed Global+Local=Total. Should a page not build successfully, the offending page is the last listed+1.

Warnings listed in blue (such as when using the not recommended layering techniques, it will compile, but warn of potential unexpected behaviours), Errors listed in red (this will not compile, and the build process halts). Note: Do not upload a zero byte file.

File Size must be small enough to fit in your Model’s Flash size. See the Status Bar or your Datasheet for your model’s Flash size. All pages’ Total Memory usage must be small enough to fit your model’s HMI allotted SRAM. See the Status Bar or your Datasheet for your model’s HMI allotted SRAM.

Due to the nature of flash, it is possible that a compiled filesize may be under the MB size (ie: 1677216 bytes) and still be shy of the available and usable Flash on the Nextion Device. Nextion may report on upload the File is too big – this is not a hardware error but the working nature of Flash. Some allowance for unusable flash pages have to made, and even more over time.

Successfully compiled Project’s *.tft file is in Nextion Editor/bianyi folder.

Display/Instruction Tabs

Selecting the Instruction Tab will load the Nextion Instruction Set in the Nextion Editor’s built in web browser. (Internet connection is required). Selecting the Display tab will take you back to the Nextion Editor Main Interface.

Status Bar

The Status Bar at the bottom contains three segments. The character encoding, the quick details of the Nextion Model selected, and the Design Canvas mouse coordinates. Clicking on Encoding will launch the DISPLAY tab of Device Settings. The Nextion Model details provide quick design specifications – limits of Project SRAM and Flash is useful to be mindful of.

Debug / Simulator Overview


  1. Simulated Nextion
  2. Operations Menu
  3. Command Redirection
  4. Input Encoding
  5. Instruction Input
  6. Simulator Return
  7. User MCU Return
  1. Input Selection
  2. Connected Nextion Identification
  3. Waveform Generator
  4. Waveform Generator Options
  5. Nextion Address
  6. Simulator Backlight and Sleep
  7. Saved Nextion Inputs

1. Simulated Nextion

  • This is a simulation – this is not an emulation.
  • Purpose of the simulation is to aid in debugging commands
  • Timers will not be precision under any Windows OS
  • RTC is simulated, GPIO is not simulated
  • EEPROM is simulated with file located Nextion Editor/eeprom.bin
  • Note: EEPROM adheres to 4 byte boundaries when writing
    Users may write to any address, but must care for data until boundary.

2. Operations Menu

  • Upload, Synchronize RTC time and Reboot device.

3. Command Redirection

  • Simulator only, Nextion device only, or both.
  • Only one (Nextion device or User MCU) can be connected at a time
    When one is selected, the other is not available.

4. Input Encoding

  • Character Encoding to use for input

5. Instruction Input

  • text command input of any non-block Instructions (excludes if, for and while)
  • Toggle hex mode to ensure byte precision in input.
    (Answers the question of how to input less frequently used characters)

6. Simulator Return

  • Any Return Data or print commands from Simulator will display here
  • Expected to be sufficient to aid in the debugging process
  • Not expected to be full trace logs (Simulator – not emulator)
  • Options added in v0.53 of the Nextion Editor
    View in Hex or String format
    View Line by Line (ÿÿÿ terminations), or by Total bytes in Hex
    Context Menu (right click) to: Copy HEX, Copy STR, Copy HEX+STR

7. User MCU Return

  • Any Return Data or print commands from Nextion/MCU will display here
  • Expected to be sufficient to aid in the debugging process
  • Not expected to be full trace logs (Simulator – not emulator)
  • Options added in v0.53 of the Nextion Editor
    View in Hex or String format
    View Line by Line (ÿÿÿ terminations), or by Total bytes in Hex
    Context Menu (right click) to: Copy HEX, Copy STR, Copy HEX+STR

8. Input Selection

  • Keyboard input is the default simulator input method.
  • Toggle to User MCU input to have user MCU interact with Simulator
    Select Com Port of user MCU, MCU operating baud rate and then Start
  • Only one (Nextion device or User MCU) can be connected at a time
    When one is selected, the other is not available.
  • Cut, Copy, Paste and Delete added to right click context menu.

9. Connected Nextion Identification

  • When Nextion is connected to Simulator, portions of connect string is shown here.

10. Waveform Generator

  • Click here to show the Waveform Generator

11. Waveform Generator Options

  • Sinewave or random waveform input at selected intervals.
  • Expected to be sufficient to aid in the debugging process
  • Not expected to be an oscilloscope (Simulator – not emulator)

12. Nextion Address

  • Default is 0 – Nextion normal mode, 256 to 2815 in address mode.
  • Address will only apply to specialized advanced applications.