April 13th: It's that time again e621! The 2025 staff drive is now OPEN! Please get your resumes and forklift licenses ready and head here to apply.
April 9th: Our dedicated FurID gallery is now live. Thank you all for the submissions to our little April Fool's prank, we hope you had as much fun as we did!
April 13th: It's that time again e621! The 2025 staff drive is now OPEN! Please get your resumes and forklift licenses ready and head here to apply.
April 9th: Our dedicated FurID gallery is now live. Thank you all for the submissions to our little April Fool's prank, we hope you had as much fun as we did!
April 13th: It's that time again e621! The 2025 staff drive is now OPEN! Please get your resumes and forklift licenses ready and head here to apply.
April 9th: Our dedicated FurID gallery is now live. Thank you all for the submissions to our little April Fool's prank, we hope you had as much fun as we did!
April 7th:It's that time again e621! The 2025 staff drive will be opening later this week! Please get your resumes and forklift licenses ready and keep an eye on the news/forums. Hope to see some fresh meat for the salt mines.
Feb 26th:A new bill in Arizona is making its way through the Senate that would force sites like e621 to implement mandatory age verification for all users—or face potential lawsuits. This system would require third-party vendors to verify every user’s age through a government database. Not only is this a massive violation of privacy, but it also introduces serious risks, including identity theft through phishing schemes and other malicious methods. Worse still, we would have no control over ensuring that user data is permanently deleted after verification.
Since e621 operates out of Arizona, this law would almost certainly impact us if it passes. If you want to help ensure that we can continue serving you without being forced to collect personal information, we urge you to contact Arizona’s senators and ask them to vote NO on this bill.
Feb 26th:A new bill in Arizona is making its way through the Senate that would force sites like e621 to implement mandatory age verification for all users—or face potential lawsuits. This system would require third-party vendors to verify every user’s age through a government database. Not only is this a massive violation of privacy, but it also introduces serious risks, including identity theft through phishing schemes and other malicious methods. Worse still, we would have no control over ensuring that user data is permanently deleted after verification.
Since e621 operates out of Arizona, this law would almost certainly impact us if it passes. If you want to help ensure that we can continue serving you without being forced to collect personal information, we urge you to contact Arizona’s senators and ask them to vote NO on this bill.
Jan 7th: Small update to the Uploading Guidelines today: We now no longer allow paintovers of AI generated content. Or in other words AI generated content that has been edited to some degree by humans.
Jan 7th: Small update to the Uploading Guidelines today: We now no longer allow paintovers of AI generated content. Or in other words AI generated content that has been edited to some degree by humans.
Dec 1st: If your account has been hit in the most recent ban wave of compromised accounts please reach out to us at management[at]e621.net and we'll help you get your account back. If you've already contacted us give us a moment to get to you, though if it takes longer than a day for us to get back to you do feel free to reach out again! Dec 2nd: If you got got and suddenly aren't able to see any of our exquisite selection of sausage and taco posts double check that Safe Mode is disabled in your account settings (Account -> Settings -> Safe mode [right above the blacklist text box]).
Dec 1st: If your account has been hit in the most recent ban wave of compromised accounts please reach out to us at management[at]e621.net and we'll help you get your account back. If you've already contacted us give us a moment to get to you, though if it takes longer than a day for us to get back to you do feel free to reach out again! Dec 2nd: If you got got and suddenly aren't able to see any of our exquisite selection of sausage and taco posts double check that Safe Mode is disabled in your account settings (Account -> Settings -> Safe mode [right above the blacklist text box]).
Oct 24th: Did you know that as of this news update, 30.8k posts have been uploaded by 5.2k verified artists? Read our Artist Verification page to learn how to get faster approvals and a verified checkmark on your posts.
Oct 24th: Did you know that as of this news update, 30.8k posts have been uploaded by 5.2k verified artists? Read our Artist Verification page to learn how to get faster approvals and a verified checkmark on your posts.
July 12th: Very important rules update: Any explicit content featuring young humans (and everything human-like) is now strictly forbidden from being uploaded. For all details, please see this thread
April 2nd:The politicians in Arizona are about to sign into law a bill that would mandate sites like e621 to either impose age verification on all users or be at a risk of lawsuits. Such system would be required to go through third party vendors, who in turn must go through a government database to verify every user's age. This is not only a major violation of privacy, but it also opens up a very real danger of identity theft through phishing schemes and other methods, not to mention that we would not be able to control any of that information to make sure it is permanently deleted after age verification is complete.
Unfortunately, Arizona is the state out of which e621 operates, which means that this law will almost certainly affect us if it is to pass. If want to help us ensure that this site can continue to serve you without being required to know who you are, please ask the Arizona governor to veto this bill.
Please, help us get the word out by letting others know about this issue.
March 15th: The 2024 Staff Drive is now open! We will be accepting applications until the 29th of March. Check out the forum post here.
Dec 31st: Due to the current legal situation in North Carolina and the uncertainty surrounding it, we will be blocking access to e621.net from North Carolina until we can consult with our legal counsel on this matter. We did not come to this decision lightly and we will do what we can, as we can, to rectify and remedy this situation so that we can restore access to those users that are affected by this matter. We sincerely apologize for this inconvenience and will have an update as soon as possible.
Sep 29th: We've just published some updates to the CoC, you can find and discuss the changes here and as usual the actual document is located here.
Dec 31st: Due to the current legal situation in North Carolina and the uncertainty surrounding it, we will be blocking access to e621.net from North Carolina until we can consult with our legal counsel on this matter. We did not come to this decision lightly and we will do what we can, as we can, to rectify and remedy this situation so that we can restore access to those users that are affected by this matter. We sincerely apologize for this inconvenience and will have an update as soon as possible.
Sep 29th: We've just published some updates to the CoC, you can find and discuss the changes here and as usual the actual document is located here.
May 15th: We're planning to do some housekeeping with old, still pending aliases and implications. If you have any old requests still pending have a look at this thread for the details.
May 24th: We've recently been made aware of a document being shared that contains login credentials for e621. We have not been breached, and the document contains login credentials obtained from other sources and previous breaches on other sites and services, much of which has already been publicly available for some time. However, if you've used the same password with the same username elsewhere, update your passwords ASAP. If your account has been banned as compromised, then you have been affected by this incident. Just follow the instructions in the ban message and we'll get you your account back in no time.
May 15th: We're planning to do some housekeeping with old, still pending aliases and implications. If you have any old requests still pending have a look at this thread for the details.
May 15th: We're planning to do some housekeeping with old, still pending aliases and implications. If you have any old requests still pending have a look at this thread for the details.
Mar 17th: New Code of Conduct is now live! Changes are too numerous to really list here, but the gist is basically we entirely rewrote it to make it shorter and clearer, while not changing much. Discuss the changes here
Mar 17th: New Code of Conduct is now live! Changes are too numerous to really list here, but the gist is basically we entirely rewrote it to make it shorter and clearer, while not changing much. Discuss the changes here
Apr 18th: A malicious person has been claiming to be doxxing artists with personal information obtained from e621. We do not store any personal information beyond the basic details associated with any user account, like the sign up email address, username, and some IPs addresses to help with moderation. If you have been contacted by said person, please ignore them and do not hesitate to reach out to us via [email protected]. We will help you as much as possible with any questions you might have.
Mar 17th: New Code of Conduct is now live! Changes are too numerous to really list here, but the gist is basically we entirely rewrote it to make it shorter and clearer, while not changing much. Discuss the changes here
Mar 20th: [Closed] We're looking for some volunteers to help tackle the ever growing workload of the site! If you're interested in maybe offering a hand have a look at this thread for the details. Thank you!
Mar 17th: New Code of Conduct is now live! Changes are too numerous to really list here, but the gist is basically we entirely rewrote it to make it shorter and clearer, while not changing much. Discuss the changes here
Apr 12th: [Done] Site Maintenance Starting at 8:00AM GMT-7 (3:00PM UTC) the site will be going down for scheduled maintenance. Sorry about the somewhat frequent maintenance lately. This should be the last (planned) one for a while.
Mar 20th: [Closed] We're looking for some volunteers to help tackle the ever growing workload of the site! If you're interested in maybe offering a hand have a look at this thread for the details. Thank you!
Mar 17th: New Code of Conduct is now live! Changes are too numerous to really list here, but the gist is basically we entirely rewrote it to make it shorter and clearer, while not changing much. Discuss the changes here
Mar 27th: [Done] Starting at 10:00AM GMT-7 (5:00PM UTC) the site will be going down for maintenance, the estimated downtime is about 1 hour. We're switching out the network card of our main database server.
Mar 20th: We're looking for some volunteers to help tackle the ever growing workload of the site! If you're interested in maybe offering a hand have a look at this thread for the details. Thank you!
Mar 17th: New Code of Conduct is now live! Changes are too numerous to really list here, but the gist is basically we entirely rewrote it to make it shorter and clearer, while not changing much. Discuss the changes here
Mar 17th: New Code of Conduct is now live! Changes are too numerous to really list here, but the gist is basically we entirely rewrote it to make it shorter and clearer, while not changing much. Discuss the changes here
Starting at 8:30AM GMT-7 (3:30PM UTC) the site will be going down for some scheduled maintenance. We will use that time to upgrade our database server.
If you are an artist uploading your own work, please tag yourself. Otherwise, people cannot easily find the rest of your work. It helps you; it helps us.
Jan 15: For everyone using LastPass: We've recently seen an uptick in spammers on the forum using breached accounts, and from speaking with a few of the people affected it appears that the common thread for them is that they used LastPass. It is very likely the vaults from the December hack are being breached now, if you use LastPass go and change all your passwords now.
If you are an artist uploading your own work, please tag yourself. Otherwise, people cannot easily find the rest of your work. It helps you; it helps us.
Dec 26: Some major changes for how the video_games tag operates are going into effect, with the tag being automatically removed from all images today. The images are being kept, and other more specific tags are already in place. See the wiki page and the forum thread for more info and the reasons behind the change.
If you are an artist uploading your own work, please tag yourself. Otherwise, people cannot easily find the rest of your work. It helps you; it helps us.
If you are an artist uploading your own work, please tag yourself. Otherwise, people cannot easily find the rest of your work. It helps you, it helps us.
June 8th: Small update to the Code of Conduct: The creepy comments rule has been reworked into Inappropriate comments. You can read about the changes here
Breaking News: MalwareBytes Premium is currently flagging static1.e621.net as compromised. This is a false positive and you can simply add an exception for it to get all images to load again. We're already in talks with MWB to have us removed from their list but it will take a bit longer until that is done.
If you are an artist uploading your own work, please tag yourself. Otherwise, people cannot easily find the rest of your work. It helps you, it helps us.
June 8th: Small update to the Code of Conduct: The creepy comments rule has been reworked into Inappropriate comments. You can read about the changes here
If you are an artist uploading your own work, please tag yourself. Otherwise, people cannot easily find the rest of your work. It helps you, it helps us.
June 8th: Small update to the Code of Conduct: The creepy comments rule has been reworked into Inappropriate comments. You can read about the changes here
June 8th: Small update to the Code of Conduct: The creepy comments rule has been reworked into Inappropriate comments. You can read about the changes here
June 8th: Small update to the Code of Conduct: The creepy comments rule has been reworked into Inappropriate comments. You can read about the changes here
June 8th: Small update to the Code of Conduct: The creepy comments rule has been reworked into Inappropriate comments. You can read about the changes here
July 26th: Posts are currently still importing into the search index after some required maintenance. Any currently missing posts will show up again shortly.
May 26th: We're currently experiencing a sizable DDoS attack. Please excuse the cloudflare captchas popping up in places. We're working hard at getting this fixed asap.
May 26th: We're currently experiencing a sizable DDoS attack. Please excuse the cloudflare captchas popping up in places. We're working hard at getting this fixed asap.
March 19th: The first Lore tags have been implemented and are ready to be used. Please have a quick gander at the Lore Tags Help Page to ensure you're using them correctly.
March 6th: Welcome to the new e621. If you've found a bug, please report it on the forum in the bug reports category.
We made a short FAQ here for all your questions on how to use new features
July 3rd: Because it has become relevant again: We do not have an official facebook page. If you find a page that pretends to be affiliated with e621.net be aware that it's fake.
If you wish to contact us for anything please be sure to use one of our official channels as outlined on our Contact page.
March 5th: Welcome to the new e621. If you've found a bug, please report it on the forum in the bug reports category.
July 3rd: Because it has become relevant again: We do not have an official facebook page. If you find a page that pretends to be affiliated with e621.net be aware that it's fake.
If you wish to contact us for anything please be sure to use one of our official channels as outlined on our Contact page.
March 5th: The site has been placed in read only mode while content is migrated to the new site.
February 12th: Our new beta is nearing completion, and with it come a few changes and calls for help. Information can be found here
Lore tags will finally be implemented, for details click here
As will be transgender tags, we have a thread dedicated for finding which to use here
July 3rd: Because it has become relevant again: We do not have an official facebook page. If you find a page that pretends to be affiliated with e621.net be aware that it's fake.
If you wish to contact us for anything please be sure to use one of our official channels as outlined on our Contact page.
February 12th: Our new beta is nearing completion, and with it come a few changes and calls for help. Information can be found here
Lore tags will finally be implemented, for details click here
As will be transgender tags, we have a thread dedicated for finding which to use here
July 3rd: Because it has become relevant again: We do not have an official facebook page. If you find a page that pretends to be affiliated with e621.net be aware that it's fake.
If you wish to contact us for anything please be sure to use one of our official channels as outlined on our Contact page.
July 3rd: Because it has become relevant again: We do not have an official facebook page. If you find a page that pretends to be affiliated with e621.net be aware that it's fake.
If you wish to contact us for anything please be sure to use one of our official channels as outlined on our Contact page.
June 22nd: We will be updating our tags dickgirl and cuntboy to be less vulgar. There won't be any changes to the current use of those tags, but there will be a short time window where some aliases and implications won't work as we update everything. For further details please see this thread.
June 22nd: We will be updating our tags dickgirl and cuntboy to be less vulgar. There won't be any changes to the current use of those tags, but there will be a short time window where some aliases and implications won't work as we update everything. For further details please see this thread.
May 26th: We had a outage with the image server earlier, but it seems to have subsided. We'll be keeping a close eye on it, hopefully it will remain stable.
May 26th: We had a outage with the image server earlier, but it seems to have subsided. We'll be keeping a close eye on it, hopefully it will remain stable.
May 14th: We're aware of connection issues to our page. These issues are localized to the french ISP "Free", and hopefully they are working to fix the routing issues soon. This is not something we can help with or affect in any way. If you want a workaround try using a VPN in the meantime.
May 14th: We're aware of connection issues to our page. These issues are localized to the french ISP "Free", and hopefully they are working to fix the routing issues soon. This is not something we can help with or affect in any way. If you want a workaround try using a VPN in the meantime.
March 6th: Small stealth update to the page: We have increased the number of possible sources from 5 to 10. In cases where a piece of art can be found in more than one place you can now add even more sources to any given image!
May 14th: We're aware of connection issues to our page. These issues are localized to the french ISP "Free", and hopefully they are working to fix the routing issues soon. This is not something we can help with or affect in any way. If you want a workaround try using a VPN in the meantime.
March 6th: Small stealth update to the page: We have increased the number of possible sources from 5 to 10. In cases where a piece of art can be found in more than one place you can now add even more sources to any given image!
March 6th: Small stealth update to the page: We have increased the number of possible sources from 5 to 10. In cases where a piece of art can be found in more than one place you can now add even more sources to any given image!
November 30th: Small update to the page! The category of any existing tags can no longer be changed with the use of metatags, this must now be done through the Tags page instead. Click here for a short guide on how to do that.
November 30th: Small update to the page! The category of any existing tags can no longer be changed with the use of metatags, this must now be done through the Tags page instead. Click here for a short guide on how to do that.
November 13th: We had an outage earlier due to a brownout at our host's datacenter, which then caused our servers to fail booting up. After we finally solved that issue we decided to directly perform our scheduled maintenance, which is also finished now. Thank you all for your patience!
November 13th: We had an outage earlier due to a brownout at our host's datacenter, which then caused our servers to fail booting up. After we finally solved that issue we decided to directly perform our scheduled maintenance, which is also finished now. Thank you all for your patience!
August 25th: Small update to the rules to clarify that vote cheating is, in fact, against the rules. Click here to read what exactly changed.
One week from today e621 will be going down for prolonged server maintenance.
Downtime will begin at 15:00 UTC (that's 08:00 MST/GMT-7, local server time) and will last approximately six hours.
We're going to be performing a wide array of long overdue hardware and software upgrades - and doing it all at once so no further prolonged downtime is needed for a while.
August 25th: Small update to the rules to clarify that vote cheating is, in fact, against the rules. Click here to read what exactly changed.
August 13th: Please remember to help us keep this place enjoyable for everyone. If you find bad behavior be sure to report them using the existing tools!
Not sure how to file a report? The Flag for Deletion tool confuses you? Want to check if someone reported it already, or if the user already got disciplined for it? Check here for help on all of that!
August 13th: Please remember to help us keep this place enjoyable for everyone. If you find bad behavior be sure to report them using the existing tools!
Not sure how to file a report? The Flag for Deletion tool confuses you? Want to check if someone reported it already, or if the user already got disciplined for it? Check here for help on all of that!
April 21st: Please don't use the 48h FFD reason if you wish to flag your own upload as an inferior version to something else. The custom reason is only there for the rare occasion that an upload needs to be deleted permanently, not just replaced with a better/different version.
April 21st: Please don't use the 48h FFD reason if you wish to flag your own upload as an inferior version to something else. The custom reason is only there for the rare occasion that an upload needs to be deleted permanently, not just replaced with a better/different version.
February 26th: Ratte has removed a ton of old records recently. If you see you've been getting a record "again" please check first that it doesn't say the record has been removed or updated. If the subject uses either of those words your record was either deleted or has been downgraded from a negative to a neutral.
Missed the update about decaying records? Check here for details.
April 21st: Please don't use the 48h FFD reason if you wish to flag your own upload as an inferior version to something else. The custom reason is only there for the rare occasion that an upload needs to be deleted permanently, not just replaced with a better/different version.
February 26th: Ratte has removed a ton of old records recently. If you see you've been getting a record "again" please check first that it doesn't say the record has been removed or updated. If the subject uses either of those words your record was either deleted or has been downgraded from a negative to a neutral.
Missed the update about decaying records? Check here for details.
April 21st: Please don't use the 48h FFD reason if you wish to flag your own upload as an inferior version to something else. The custom reason is only there for the rare occasion that an upload needs to be deleted permanently, not just replaced with a better/different version.
February 26th: Ratte has removed a ton of old records recently. If you see you've been getting a record "again" please check first that it doesn't say the record has been removed or updated. If the subject uses either of those words your record was either deleted or has been downgraded from a negative to a neutral.
Missed the update about decaying records? Check here for details.
February 26th: Ratte has removed a ton of old records recently. If you see you've been getting a record "again" please check first that it doesn't say the record has been removed or updated. If the subject uses either of those words your record was either deleted or has been downgraded from a negative to a neutral.
Missed the update about decaying records? Check here for details.
October 21st: Important Rule Change for all uploaders: Paid content is now always DNP regardless of age. Please see this thread for more details.
October 21st: Important Rule Change for all uploaders: Paid content is now always DNP regardless of age. Please see this thread for more details.
October 19th: We recently added the ability to report posts to help ensure admin attention can be better directed to submissions that require them. See here for more details.
October 18th: Since it has come up recently: Please do not tag Pokémon or Digimon as their real world counterparts, but only as the family. Eg persian is not a cat but a feline, renamon is not a fox but a canine, etc.
This is purely to ensure that actual "real" animals can be found without having all those fantasy animals show up as well.
October 19th: We recently added the ability to report posts to help ensure admin attention can be better directed to submissions that require them. See here for more details.
October 18th: Since it has come up recently: Please do not tag Pokémon or Digimon as their real world counterparts, but only as the family. Eg persian is not a cat but a feline, renamon is not a fox but a canine, etc.
This is purely to ensure that actual "real" animals can be found without having all those fantasy animals show up as well.
October 18th: Since it has come up recently: Please do not tag Pokémon or Digimon as their real world counterparts, but only as the family. Eg persian is not a cat but a feline, renamon is not a fox but a canine, etc.
This is purely to ensure that actual "real" animals can be found without having all those fantasy animals show up as well.
July 15th: We're aware of the pool names vandalism. It will be cleaned up asap. Thank you for your patience.
June 9th: New Code of Conduct changes! All information and changes can be found here.
TL;DR: Too long for TL;DR, please see the thread. All changes are color coded so it's easy and quick to skim over everything relevant!
May 26th: Old Code of Conduct changes. All information and changes can be found here.
TL;DR: Old negative records (including the ones for suspensions/temp bans) are now up for deletion if the user hasn't broken those same rules again in a long time.
May 26th: New Code of Conduct changes! All information and changes can be found here.
TL;DR: Old negative records (including the ones for suspensions/temp bans) are now up for deletion if the user hasn't broken those same rules again in a long time.
April 29: Old Code of Conduct changes. All information and changes can be found here.
TL;DR: The rule on impersonating staff was expanded to include users, rules governing name changes and solicitation have been added.
May 26th: Old Code of Conduct changes! All information and changes can be found here.
TL;DR: Old negative records (including the ones for suspensions/temp bans) are now up for deletion if the user hasn't broken those same rules again in a long time.
April 29: Old Code of Conduct changes. All information and changes can be found here.
TL;DR: The rule on impersonating staff was expanded to include users, rules governing name changes and solicitation have been added.
April 29: New Code of Conduct changes! All information and changes can be found here.
TL;DR: The rule on impersonating staff was expanded to include users, rules governing name changes and solicitation have been added.
February 24: In response to a potential information leak at CloudFlare we are requesting that users change their passwords. Please see the forum post for more details.
April 29: New Code of Conduct changes! All information and changes can be found here.
**TL;DR: The rule on impersonating staff was expanded to include users, rules governing name changes and solicitation have been added.
February 24: In response to a potential information leak at CloudFlare we are requesting that users change their passwords. Please see the forum post for more details.
April 29: New Code of Conduct changes! All information and changes can be found here. TL;DR: The rule on impersonating staff was expanded to include users, rules governing name changes and solicitation have been added.
February 24: In response to a potential information leak at CloudFlare we are requesting that users change their passwords. Please see the forum post for more details.
April 29: New Code of Conduct changes! All information and changes can be found here. TL;DR: The rule on impersonating staff was expanded to include users, rules governing name changes and solicitation have been added.
February 24: In response to a potential information leak at CloudFlare we are requesting that users change their passwords. Please see the forum post for more details.
February 24: In response to a potential information leak at CloudFlare we are requesting that users change their passwords. Please see the forum post for more details.
November 4th, 2016: All issues with takedowns have been fixed. If you have a pending takedown request that was created before November 1st please contact us asap.
May 14, 2016: Small Code of Conduct update, we merged part of the DNP-List with Posting Abuse, details here.
February 24: In response to a potential information leak at CloudFlare we are requesting that users change their passwords. Please see the forum post for more details.
November 4th, 2016: All issues with takedowns have been fixed. If you have a pending takedown request that was created before November 1st please contact us asap.
May 14, 2016: Small Code of Conduct update, we merged part of the DNP-List with Posting Abuse, details here.
February 22: In response to a potential information leak at CloudFlare we are requesting that users change their passwords. Please see the forum post for more details.
November 4th, 2016: All issues with takedowns have been fixed. If you have a pending takedown request that was created before November 1st please contact us asap.
May 14, 2016: Small Code of Conduct update, we merged part of the DNP-List with Posting Abuse, details here.
February 22: In response to a potential information at CloudFlare we are requesting that users change their passwords. Please see the forum post for more details.
November 4th, 2016: All issues with takedowns have been fixed. If you have a pending takedown request that was created before November 1st please contact us asap.
May 14, 2016: Small Code of Conduct update, we merged part of the DNP-List with Posting Abuse, details here.
February 8: Starting at 12PM GMT-7 we're taking e621 down for some routine maintenance. We're upgrading the networking to one of the servers. Estimated downtime should be between 30 minutes to an hour - keep an eye on e621's Twitter account for updates!
November 4th, 2016: All issues with takedowns have been fixed. If you have a pending takedown request that was created before November 1st please contact us asap.
May 14, 2016: Small Code of Conduct update, we merged part of the DNP-List with Posting Abuse, details here.
November 4th: All issues with takedowns have been fixed. If you have a pending takedown request that was created before November 1st please contact us asap.
May 14: Small Code of Conduct update, we merged part of the DNP-List with Posting Abuse, details here.
October 31: We have found a bug with our takedown system. If you have been waiting for more than 24h that a takedown of yours is getting handled please read here.
May 14: Small Code of Conduct update, we merged part of the DNP-List with Posting Abuse, details here.
May 14: Small Code of Conduct update, we merged part of the DNP-List with Posting Abuse, details here.
May 13: Small update to the page, the "roaming" option now actually does something, if you don't have it active and your IP changes you will get logged out. Coincidentally, we logged everybody out just now.
Trouble with your password? Reset it here or contact us.
May 14: Small Code of Conduct update, we merged part of the DNP-List with Posting Abuse, details here.
May 13: Small update to the page, the "roaming" option now actually does something, if you don't have it active and your IP changes you will get logged out. Coincidentally, we logged everybody out just now.
Trouble with your password? Reset it here or contact us.
September 7: e621 will briefly be going down for server maintenance tomorrow starting at 9AM GMT-7 (4PM UTC). We're going to be doubling the amount of storage available for content on e621's servers. Shouldn't take any more than 15-30 minutes.
May 14: Small Code of Conduct update, we merged part of the DNP-List with Posting Abuse, details here.
May 13: Small update to the page, the "roaming" option now actually does something, if you don't have it active and your IP changes you will get logged out. Coincidentally, we logged everybody out just now.
Trouble with your password? Reset it here or contact us.
May 14: Small Code of Conduct update, we merged part of the DNP-List with Posting Abuse, details here.
May 13: Small update to the page, the "roaming" option now actually does something, if you don't have it active and your IP changes you will get logged out. Coincidentally, we logged everybody out just now.
Trouble with your password? Reset it here or contact us.
You must be 18 years or older and agree to the terms of service to access this website.
Content that is commonly considered objectionable is blacklisted by default.
You may remove tags from this blacklist using the corresponding menu item.