Remove or relax rate restrictions
Just encountered for the first time the 5 minute timeout on using the tool too quickly / much. Unless there is a severe cost or risk of abuse please consider relaxing or removing altogether these rate restrictions as speed and ease of use are key reasons for using this versus other methods.
Log in to comment and vote
Comments6
haloeight
Nov 12, 2025
This really needs to be fixed. If the rate limit is encountered on a particular tweet it seems as though you can’t even capture that tweet after waiting for the designated amount of time, it seems as though the code focuses on the tweet link that caused the limit to be triggered and you have to just move onto something else. Even if you go back to paste the tweet that was problematic it won’t work.
Kevin Wu
Nov 20, 2025
Hi, Sorry for the inconvenience! The current limit is mainly in place to prevent too-frequent refreshes of the API endpoint. In most cases, Manual web screenshots won’t be affected.and things should return to normal once the waiting period ends.
Could you share a screenshot or link of a short screen recording of the issue? That would really help me diagnose what’s happening.Thank you.
haloeight
Oct 14, 2025
I then found on reattempting the timeout doubles which is pretty bad in terms of restrictions without warning.
Kevin Wu
Oct 14, 2025
Hi @haloeight thanks feedback and sorry about that. we’re actively optimizing this.
About rate limit, we’ve restored it after detecting some automated script abuse, This rate limit is designed to ensure normal usage on the website and to prevent unnecessary resource waste.
We’ll review the limits to make them more flexible, and our API Plan also allows for higher request rates if need faster access.