Ship to Worldwide
ESP32 S3 touch screen 2.41 inch
⚠️If you need technical support, you can get a quicker response on our GitHub (the tech team will check it directly). Please provide your Tax/Personal ID (if available), this will expedite the shipment of your order.
Instructions Before Order
Instructions Before Order
If you order the wrong product or want to add another or change your shipping address, please re-edit the correct information and place a new order, then contact us to cancel the incorrect order.
If you have a tax ID or personal ID please provide as much as possible, otherwise, if your country requires this information we will block your order and contact you via email, which will slow down the shipment.
We strongly recommend choosing DHL or FedEx if your order is over $200.
Generally, except for DHL or FedEx, we will automatically split orders over $150-200 into two packages due to customs clearance, loss prevention issues, etc.
For more please check here
Shipping & Delivery
Shipping & Delivery
Methods & Delivery Time
- Standard Express/ YanWen: 25-30 Days
- EUB: 25-30 Days
- YunTu Express : 10-20 Days
(Company name can't be used consignee) - DHL: 10-17 Days
- FedEx: 10-17 Days
Please note that all delivery times are estimated for reference only.
If you do not see one of the above shipping methods when checking out, it may be because your country does not support that shipping method, please select one of the available channels already listed or contact us for help.
Please make sure your address is fully filled in (including province and continent, which will affect the shipping time of your order)
For more details please check our shipping policy.
About Tax
About Tax
At present, the price of the platform does not include any tax.
European customers should pay attention to the tax problem after the package reaches the local country, which needs to be borne/handled by the customer, the local policy shall prevail
[orders over 150 euros may generate tax (Amount for reference only), for orders over this amount, we will not inform the customer separately, so please pay attention to it by yourself.]
Specifications
MCU | ESP32-S3R8 Dual-core LX7 microprocessor |
Wireless Connectivity | 2.4 GHz Wi-Fi & Bluetooth 5 (LE) |
Development | Arduino, PlatformIO-IDE, Micropython |
Flash | 16MB |
PSRAM | 8MB |
Language | C, C++, Lua |
Onboard functions | Boot Button + Reset + Micro SD |
2.41-inch SPI RGB AMOLED |
Active Area | 36.2*48.96mm |
Brightness | 800cd/m |
Resolution | 450(W) x RGB x 600(H) |
Interface | QSPI |
Sample Code For Reference [Github]
If you need technical support please check below link to find more details.
Size
Pin Diagram
More
[If you need extension cable, click here]
With Shell Soldered Pin
With Shell Soldered Female Pin
Basic
Only Sheild
Share
Great design
I have been using the T4-S3 boards extensively for the past few months. Have not had any issues with these fantastic little devices. Amazingly sharp screen, fast responsive touch, solid build quality. If you are starting out, the GitHub repository has everything you need to start developing your own custom, touchscreen-based applications. My suggestion is to use Visual Studio Code with the PlatformIO extension. I would give this device 10 stars, if LilyGo would add an SX1276 LoRa chip to the board - it would be the ultimate!
I like the device very much. https://www.youtube.com/watch?v=GcHdyRwgepo check video created using T4-S3
Nice product.
Burned two of these units by plugging in expansion board with pins offset by 1 row. This is very easy to do since the board is usually inside a case and you can not see the header very well. Should have keyed header, or better protection electronics to avoid this.
I would like to buy two replacement board only. Can you provide info?
Hi Sir,
Please contact our support team and they will help you.
You can check our ' Contact Us' page, or email to orders@lilygo.cc
Docs are often wrong or incomplete. You have to wait for someone to make a youtube or figure out the drivers and the correct gpio pins.
Hi, can I know which part of the error documentation you are referring to?
We have provided sample code for reference [ Github].
If you have already checked it but still need help please contact our support team or start a thread in our community and our team of engineers will help you.