Early Access New Firmware for Archer AX53 Introduces Web Protection Whitelist, ECO Mode v2, and More
Hello everyone!
We are pleased to announce a pre-release firmware update for the Archer AX53 V1, introducing new features such as the Web Protection Whitelist, ECO Mode v2, and more.
All users are encouraged to upgrade to the latest firmware and share your feedback. This is crucial for our continuous product improvement! We look forward to your experience!
Download the update now and experience your router's new features!
New Features/Enhancements:
1. Third-Party VPN Client Integration (NordVPN & Surfshark)
Added native support for NordVPN and Surfshark configurations. You can now set up your VPN client using either an Access Token or dedicated Account Credentials directly.
2. ECO Mode v2
Smart ECO Mode (Default): Automatically adjusts power consumption and turns off status LEDs based on real-time network traffic, minimizing energy use without affecting performance.
Custom Profiles & Schedules: Choose from multiple power-saving profiles and customize active time periods to match your daily schedule.
3. Admin Password Recovery
We have introduced new methods to recover your local administrator password, ensuring you never lose access to your router's settings. You can now choose between two secure recovery options:
Security Questions: Set up answers to predefined security questions. This allows you to quickly verify your identity and reset your password.
Email Recovery: Configure a designated email address and your own SMTP server to receive password recovery instructions directly to your inbox.
You can enable and configure these options under System > Administration.
4. Whitelist for Web Protection
Added an exception/whitelist feature to Web Protection. Added client devices can bypass web filtering and access the internet without security blocks or restrictions.
5. DHCP Detection
Having rogue or multiple active DHCP servers on a local network can cause IP conflicts and disconnects. This one-click diagnostic tool scans the LAN to detect duplicate DHCP servers, helping you quickly identify and resolve IP address conflicts.
6. HTTPS Certificate Export
When HTTPS Management is enabled, browsers may flag the local management page with a "Not Secure" warning. You can now download and export the router’s SSL certificate directly from the Web UI and install it on your PC or mobile device to eliminate browser security prompts.
7. Client Filtering by SSID in Client List
Added the ability to filter and view connected devices based on their specific wireless network (SSID).
Other Enhancements:
- Added an option in Access Control whitelist to exempt Guest Network clients.
- Added Interactive Help Tooltips with direct links to official FAQs.
Firmware Download:
Before the Upgrade
(1) Please be sure you have read the Beta Test Agreement before upgrading the pre-release firmware!
(2) For the sake of insurance, it's always recommended to save a copy of the router's Backup Config file before upgrading or downgrading.
(3) You may follow the guide to upgrade the firmware of your router. How to Upgrade the Firmware on the TP-Link Wi-Fi Routers.
(4) This version upgrade is irreversible and you cannot downgrade to the previous firmware after the upgrade.
Direct Firmware Download Link
| Archer AX53_V1 | Archer AX53_V1_1.8.0 Build 20260821 (Pre-Release Firmware) |
Additional Information
As always, we value your feedback. If you encounter any concerns during or after the router firmware upgrade, please leave a message below and include the following information. Your feedback helps us improve and provide better products and support.
Please provide detailed information, including but not limited to:
- A complete network topology diagram.
- The device's connection method and whether EasyMesh networking is enabled.
- Screenshots of relevant error messages, etc.
Thank you for your continued support and for being a member of our community.
Join Us for Our First Look at Wi-Fi 8 During Our September 30th Live Stream
Latest posts: ▷Archer BE550 V2 Enhances EasyMesh Support with Guest/IoT/MLO Extension ▷Archer BE550 V1 Supports Guest/IoT Network Extension More posts, please see: ▷Get the Ongoing Pre-release Firmware for Wi-Fi Routers Here! Contact via Messages or @Joesph-TP in your new post for urgent problems (not online 24/7). Click Recommended Solution if the post/answer helps.
Subject: Feedback on Archer AX53 V1 (Firmware 1.8.0 Build 20260821 Beta) - AP Mode Issues & UI/UX Bugs
Hello TP-Link Team,
I have been testing the 1.8.0 Build 20260821 Pre-release firmware on my Archer AX53 V1 and would like to report three issues encountered during operation:
-
Operating Mode: Access Point (AP Mode)
-
Topology: Main Router Archer AX53 (AP Mode)
-
Archer C80 (EasyMesh Satellite via Wi-Fi) Wired/Wireless Clients
1. Web GUI Login Loop (Critical)
After running stably for the first ~24 hours, the local web interface became inaccessible.
-
Symptom: Entering the correct local admin password caused the page to load briefly and redirect immediately back to the login screen without any error message.
-
Network Status: The router continued passing traffic and broadcasting SSIDs normally.
-
Resolution: A physical hardware reboot restored access. This suggests a session management / token expiration handling bug in the web daemon under AP mode after some uptime.
2. Network Map Auto-Selection Behavior (UI Inconsistency)
In previous firmware versions, clicking on the Network Map tab defaulted to selecting the Internet icon to display gateway and connection status.
-
Current Behavior: In 1.8.0, clicking Network Map automatically jumps to the Archer AX53 icon instead, requiring an extra click if the user wants to view the Internet node.
3. Client List Dropdown Filter Defaults to Blank (Mobile Web UX Bug)
Regarding the new feature "Added support for filtering clients by SSID in the Client List":
-
Current Behavior: In the mobile web interface, opening the Clients tab displays
"- Please Select -"in the dropdown filter and shows "There is no entry!", even though the badge clearly indicates connected clients (e.g., 10 clients). -
Expected Behavior: The dropdown should default to "All (x)" upon opening the tab so the full list of connected clients is immediately visible without requiring manual selection.
I hope this feedback helps refine the firmware before the official public release. Let me know if further details or specific system logs are required.
Hi I’m using an Archer AX53 V1 with the latest beta firmware, 1.8.0 Build 20260821 rel.13486(5553). I’m on a 51 Mbps symmetrical fiber-optic connection (51 Mbps download and 51 Mbps upload), and I’ve noticed that Download QoS doesn’t seem to be working properly compared to Upload QoS. When the connection is under heavy download load, the latency and jitter increase significantly, while Upload QoS seems to manage the traffic much better. The difference between Download and Upload QoS is quite noticeable during testing. I’ve attached screenshots of the firmware version and Speedtest results for reference. Could you please check if there is an issue with the Download QoS implementation in this beta firmware and consider fixing it in a future update? Thanks!
Hi TP-Link team, I’m using an Archer AX53 V1 with the latest beta firmware, 1.8.0 Build 20260821 rel.13486(5553). I’m on a 51 Mbps symmetrical fiber-optic connection (51 Mbps download and 51 Mbps upload), and I’ve noticed that Download QoS doesn’t seem to be working properly compared to Upload QoS. When the connection is under heavy download load, the latency and jitter increase significantly, while Upload QoS seems to manage the traffic much better. The difference between Download and Upload QoS is quite noticeable during testing. I’ve attached screenshots of the firmware version and Speedtest results for reference. Could you please check if there is an issue with the Download QoS implementation in this beta firmware and consider fixing it in a future update? Thanks!
connected directly to the modem
@Joseph-TP qos on but test performed when the device is connected to lan port here the download latency fixed
Reply from 8.8.8.8: bytes=64 ttl=120 seq=1 time=36.253 ms
Reply from 8.8.8.8: bytes=64 ttl=120 seq=2 time=36.211 ms
Reply from 8.8.8.8: bytes=64 ttl=120 seq=3 time=35.916 ms
Reply from 8.8.8.8: bytes=64 ttl=120 seq=4 time=36.248 ms
Reply from 8.8.8.8: bytes=64 ttl=120 seq=5 time=36.361 ms
Reply from 8.8.8.8: bytes=64 ttl=120 seq=6 time=37.321 ms
Reply from 8.8.8.8: bytes=64 ttl=120 seq=7 time=35.632 ms
Reply from 8.8.8.8: bytes=64 ttl=120 seq=8 time=36.383 ms
Reply from 8.8.8.8: bytes=64 ttl=120 seq=9 time=36.813 ms
Reply from 8.8.8.8: bytes=64 ttl=120 seq=10 time=36.403 ms
Reply from 8.8.8.8: bytes=64 ttl=120 seq=11 time=36.563 ms
Reply from 8.8.8.8: bytes=64 ttl=120 seq=12 time=36.268 ms
Reply from 8.8.8.8: bytes=64 ttl=120 seq=13 time=35.708 ms
Reply from 8.8.8.8: bytes=64 ttl=120 seq=14 time=36.333 ms
Reply from 8.8.8.8: bytes=64 ttl=120 seq=15 time=36.568 ms
Reply from 8.8.8.8: bytes=64 ttl=120 seq=16 time=36.821 ms
Reply from 8.8.8.8: bytes=64 ttl=120 seq=17 time=36.359 ms
Reply from 8.8.8.8: bytes=64 ttl=120 seq=18 time=36.352 ms
Reply from 8.8.8.8: bytes=64 ttl=120 seq=19 time=35.967 ms
Reply from 8.8.8.8: bytes=64 ttl=120 seq=20 time=35.934 ms
Reply from 8.8.8.8: bytes=64 ttl=120 seq=21 time=36.028 ms
Reply from 8.8.8.8: bytes=64 ttl=120 seq=22 time=35.966 ms
Reply from 8.8.8.8: bytes=64 ttl=120 seq=23 time=37.072 ms
Reply from 8.8.8.8: bytes=64 ttl=120 seq=24 time=36.662 ms
Reply from 8.8.8.8: bytes=64 ttl=120 seq=25 time=36.266 ms
Reply from 8.8.8.8: bytes=64 ttl=120 seq=26 time=36.755 ms
Reply from 8.8.8.8: bytes=64 ttl=120 seq=27 time=36.671 ms
Reply from 8.8.8.8: bytes=64 ttl=120 seq=28 time=37.266 ms
Reply from 8.8.8.8: bytes=64 ttl=120 seq=29 time=37.219 ms
@Pankajuuuuu My speedtest on laptop through lan port(i don't need qos, since i have gigabit line), but somehow i have higher latency?
