# Using 2 accounts to subscribe to chatGPT Plus to get twice the limit

**URL:** <https://community.openai.com/t/using-2-accounts-to-subscribe-to-chatgpt-plus-to-get-twice-the-limit/136434>\
**Category:** ChatGPT\
**Created:** [April 3, 2023, 2:34am UTC](https://community.openai.com/t/using-2-accounts-to-subscribe-to-chatgpt-plus-to-get-twice-the-limit/136434 "2023-04-03T02:34:49Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![korakot](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/korakot/32/62933_2.png) [@korakot](https://community.openai.com/u/korakot)\
**Post date:** [April 3, 2023, 2:34am UTC](https://community.openai.com/t/using-2-accounts-to-subscribe-to-chatgpt-plus-to-get-twice-the-limit/136434/1 "2023-04-03T02:34:50Z")

</div>

The current GPT-4 limit is 25 messages for 3 hours, and it’s going lower soon.

I plan to subscribe using 2 accounts, paying twice, and get twice the limit. Is this against the ToS? I ask chatGPT this, it said it should be OK. It refer to this section.

Section 4(e) states:

“You may not create more than one account to benefit from credits provided in the free tier of the Services. If we believe you are not using the free tier in good faith, we may charge you standard fees or stop providing access to the Services.”

This should apply to free tier only, not on paid subscription. Do I understand this correctly?

---

<div class="post-metadata">

**Author:** ![randomtom](https://avatars.discourse-cdn.com/v4/letter/r/50afbb/32.png) [@randomtom](https://community.openai.com/u/randomtom)\
**Post date:** [April 9, 2023, 7:56am UTC](https://community.openai.com/t/using-2-accounts-to-subscribe-to-chatgpt-plus-to-get-twice-the-limit/136434/2 "2023-04-09T07:56:28Z")

</div>

Hey, did they block your second account already?

---

<div class="post-metadata">

**Author:** ![korakot](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/korakot/32/62933_2.png) [@korakot](https://community.openai.com/u/korakot)\
**Post date:** [April 9, 2023, 2:26pm UTC](https://community.openai.com/t/using-2-accounts-to-subscribe-to-chatgpt-plus-to-get-twice-the-limit/136434/3 "2023-04-09T14:26:42Z")

</div>

No, my application for the second account needs to wait for the waitlist. So, I cannot try it yet.

---

<div class="post-metadata">

**Author:** ![richardmckinney](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/richardmckinney/32/219553_2.png) [@richardmckinney](https://community.openai.com/u/richardmckinney)\
**Post date:** [October 14, 2023, 2:28am UTC](https://community.openai.com/t/using-2-accounts-to-subscribe-to-chatgpt-plus-to-get-twice-the-limit/136434/5 "2023-10-14T02:28:13Z")

</div>

After running into the cap of 50 messages every 3 hours, I registered a second account and successfully opted into ChatGPT Plus again (i.e., for the second time).

Unfortunately, this wasn’t a successful workaround.

---

<div class="post-metadata">

**Author:** ![richardmckinney](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/richardmckinney/32/219553_2.png) [@richardmckinney](https://community.openai.com/u/richardmckinney)\
**Post date:** [October 14, 2023, 2:30am UTC](https://community.openai.com/t/using-2-accounts-to-subscribe-to-chatgpt-plus-to-get-twice-the-limit/136434/6 "2023-10-14T02:30:09Z")

</div>

Scratch that - while I’d cleared the browser cache and opted into aggressive fingerprint blocking, using the same browser was the issue.

On either a different browser or a different client/device, this approach works as intended.

---

<div class="post-metadata">

**Author:** ![vkl](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/vkl/32/232317_2.png) [@vkl](https://community.openai.com/u/vkl)\
**Post date:** [November 5, 2023, 8:15pm UTC](https://community.openai.com/t/using-2-accounts-to-subscribe-to-chatgpt-plus-to-get-twice-the-limit/136434/7 "2023-11-05T20:15:53Z")

</div>

![image](https://us1.discourse-cdn.com/openai1/original/3X/f/e/fe550b9352a990d6fc0bb059cbaf5eea522c0b0e.png)
