Stop Cooking These 10 Foods in Your Instant Pot
The Instant Pot is an incredibly convenient appliance, especially in the summer when you don't want to spend a lot of time in front of the stove. It offers multiple cooking options and features, but there are limits to its power, and some foods don't fare well in the machine. To save you time, money and having to eat something awful, we've devised this list of foods you should never cook in the Instant Pot.
Here are 10 food items and recipes you should never cook in your Instant Pot.
And for more cooking tips, check out nine cooking hacks that actually work, why you might be ruining your chef's knife and the top slow cooker mistakes to avoid.
Seafood
Shrimp is best cooked on the grill or in a sauté pan.
David Watsky/CNET
In general, seafood such as fish, oysters, shrimp, mussels and clams is just too delicate for pressure cooking and slow cooking modes. They are foods that are meant to be cooked quickly at just the right temperature, which is hard to do with an Instant Pot. A few seconds too long or at the wrong temperature, and you can end up with mush or rubbery lumps.
Besides, fish, shellfish and crustaceans are easily cooked with other methods, so breaking out the Instant Pot for them won't guarantee better results as it can for tougher meats.
The only exception is octopus and squid. Pressure cooking these tough creatures can make them tender while keeping the meat juicy. Just be sure to find a recipe that is specifically for the Instant Pot.
Fried and crispy food
Fries and other crispy foods don't work in the Instant Pot.
Elevation Burger
Unless you've purchased a specialty model, your Instant Pot is not a pressure fryer and isn't designed for the higher temperatures needed to heat cooking oil for something like crispy fried chicken. Of course, an Instant Pot is perfect for a dish like carnitas, but to get the final crisp on the meat, after you remove the meat from the Instant Pot, transfer it to a skillet and brown for a few minutes or on a baking sheet to crisp up in a hot oven. (However, if you're looking for an air fryer that will get your food nice and crispy, you can check out our tested picks for the best air fryers of 2025).
CNET
Dairy-based food
Just like in a slow cooker, most dairy products such as cheese, milk and sour cream will curdle in an Instant Pot, no matter if you use the pressure cooking setting or the slow cooking setting. Add these ingredients after the dish cooks or avoid making the recipe in the Instant Pot altogether.
There are two exceptions. One is when you're making yogurt, and that's only if you use a recipe specifically for an Instant Pot. The other is if you're making a cheesecake, and again, only if you're following an Instant Pot recipe.
Pasta and noodles
A pot of boiling water is the only way to cook pasta properly.
Getty/JannHuizenga
While you technically can cook pasta in an Instant Pot, it may come out gummy or unevenly cooked. Honestly, unless you don't have the option, boiling the pasta in a pot on a stovetop is just as fast and easy and will yield consistently better cooked pasta.
Read more: No, Salted Water Doesn't Boil Faster and 7 Other Pasta Myths
Two recipes at once
Cooking a roast with potatoes and carrots is a time-honored recipe, right? Not in this case. Don't try to cook a main dish with a side dish in your Instant Pot. They may fit in the pot together, but each food will need its own cooking time. Cooking items together will inevitably result in a dry or mushy mess.
Cakes
You aren't really baking a cake in an Instant Pot, you're steaming it. The cake will be moist -- which works for something like bread pudding -- but you won't get a nice crust on the cake or the chewy edges that everyone fights over with baked brownies. However, if you do need to throw something together for a potluck or quick family dessert, you can get a moist sponge in half an hour or so, excluding prep time.
Foods for canning
Canning, the art of cooking and sealing foods in jars, is often done in a pressure cooker. So, it may seem like a good idea to make a batch of jams, pickles or jellies in your Instant Pot. Don't do it.
With an Instant Pot, you're not able to monitor the temperature of what you're canning as you would with a regular pressure cooker. With canning, cooking and sealing the food correctly is key. Improper cooking and sealing can lead to bacteria growth that can cause food poisoning.
While you want to avoid canning with an Instant Pot, some of the newer models (like the Duo Plus) do have a sterilize setting that lets you clean baby bottles and kitchen items like jars and utensils.
Good steak
A pressure cooker is not a barbecue. An Instant Pot does great with tougher cuts of meat -- which the pressure cooker can easily break down -- but not so good with ones that are best eaten medium-rare, like a steak. Save those for the grill.
Yellow and red lentils
Not all lentils can stand up to an Instant Pot's pressure.
James Martin/CNET
We love lentils, but not all of them can be cooked in an Instant Pot. Brown and green lentils can hold up to pressure cooking, but the more delicate yellow and red versions turn to mush because they cook so quickly. Unless you're purposely making lentil soup or dhal, stick to cooking red and yellow lentils on the stove to preserve their texture and shape.
Cookies
Cookies aren't going in your Instant Pot, are they?
Getty Images
Cookies are another baked food that doesn't work when made in the Instant Pot, either on pressure cooker or slow cooker mode. Instead, try your luck with convection heat by way of a wall oven, toaster or air fryer.
Try Our AI Features
Explore what Daily8 AI can do for you:
Comments
No comments yet...
Related Articles
Forbes
an hour ago
- Forbes
3 Couple Fights That Can Silently End Relationships, By A Psychologist
Subtle but recurring conflicts chip away at a relationship's foundation. You think it's just another ... More small fight. But it becomes the very reason you drift apart. Not all breakups come crashing in with shouting matches and ultimatums. Some quietly build their case over time, fed by seemingly 'minor' fights that repeat like a broken record. They are just loud enough to irritate without sounding a loud alarm. Many couples often come to therapy feeling confused about why their relationship feels so unstable despite not having any 'big' problems. And more often than not, it's the seemingly inconsequential, everyday conflicts — the ones we tend to brush aside — that quietly shake the foundation of a relationship. Here are three fights that don't look like breakup material at the first glance but usually are, when you look deeper. 1. The 'It's Not A Big Deal' Dismissal Fight This fight looks minor. One partner brings up something that upsets them, like feeling excluded at a gathering or dismissed in a conversation, and the other replies with, 'You're overthinking it,' or 'Why make a big deal out of nothing?' It doesn't escalate. It ends quickly. But what's actually happening is a breakdown in emotional responsiveness where one partner is reaching out for attunement, and the other is pulling away. Recent research published in Psychological Reports highlights why this pattern is more harmful than it appears. A dyadic study of 240 mixed-gender couples found that perceived emotional invalidation or the persistent feeling that your emotions are dismissed or minimized, is significantly associated with increased psychological distress in both men and women. For women, notably, this distress also predicted lower relationship satisfaction, both for themselves and their partners. Emotional invalidation chips away at a person's sense of security in the relationship. Eventually, the dismissed partner may begin to doubt their own feelings, suppress their emotional needs or simply stop bringing them up because for them, it's just safer not to. What remains is silent resentment and emotional distance. What makes this kind of fight especially insidious is that it's rarely seen as serious. But its cumulative impact, especially when it follows a gendered pattern, is highly significant. As the research shows, the distress caused by these micro-invalidations have an outsized effect, impacting how both partners experience the relationship. 2. The Scorekeeping Fight No one enters a relationship planning to keep score. But over time, it can creep in quietly through familiar refrains: These are not just complaints. They're emotional invoices. And they reveal a deeper shift from connection to calculation. Scorekeeping often stems from a real imbalance with one partner feeling emotionally or practically unsupported. But instead of leading to open dialogue, it morphs into a tit-for-tat dynamic, where past sacrifices are tallied and present generosity is withheld until it's been 'earned.' A 2019 study published in the Journal of Social and Personal Relationships lends strong evidence to how corrosive this mindset can be. In a 28-day daily diary study of cohabiting couples, researchers found that individuals with a high 'exchange orientation,' such as those who closely monitor the give-and-take in their relationship, experienced lower intimacy on days when conflict occurred, compared to those with a low exchange orientation. Even after accounting for mood or general negativity, the scorekeeping mindset itself made conflicts feel heavier, and more personally threatening. In other words, it's not just the conflict that strains the relationship, it's the lens through which the conflict is viewed. When a partner is attuned to fairness in a transactional sense, even small disagreements may be perceived as evidence of imbalance or disrespect. This can escalate minor conflicts into emotionally disproportionate responses. Over time, this leads to a relational atmosphere where giving is no longer an act of love but a conditional exchange. Generosity starts requiring repayment. Gratitude turns into bargaining. And intimacy becomes harder to access, especially during moments of tension — just when it's needed the most. And that's when the partnership stops feeling like a safe space and starts feeling like a negotiation table. 3. The Same Fight But Different Variations Some couples don't fight often. But when they do, it's the same fight over and over again. It simply shows up in different disguises. One week it's about the dishes. Next, it's about parenting. Then it's how late someone got home, or how a text went unanswered. The topics change, but the emotional undercurrent stays the same: one or both partners feel unimportant, unseen or unacknowledged. These repeated fights are rarely about surface-level issues. They're about unmet emotional needs. The need to feel respected, prioritized, emotionally safe. But instead of addressing the deeper pattern, the couple gets stuck in the specifics. They argue about what happened, not what's happening between them right now at a deeper level. According to Dr. John Gottman, when this dynamic becomes chronic, it creates a relational state known as negative sentiment override — a condition in which partners develop a consistently negative filter through which they interpret each other's behavior. Even neutral or well-meaning gestures are perceived as selfish, passive-aggressive or hostile. A partner's delay is not seen for what it is, instead, they're seen as inconsiderate. A missed call doesn't feel like just an oversight, it feels like rejection. When this pattern takes hold, it's not the fight itself that wears couples down. It's the emotional exhaustion of reliving the same unresolved conflict in different forms. The frustration compounds. The empathy erodes. And what could have been an opportunity for repair becomes yet another loop in an endless cycle. So, What Can You Do? If you've recognized yourself in any of these fights, it doesn't mean your relationship is doomed. But it does mean it's time to pay attention. These patterns tend to compound over time instead of correcting themselves. Here's what helps, and how you can implement it: Breakups often happen 'emotionally' before they happen 'logistically.' The couples that make it are the ones who notice when the quiet fights start to sound louder than they used to, and take aligned action to save the relationship. Think you're doing fine as a couple but still feel a little disconnected? Take this research-backed Relationship Satisfaction Scale to see how emotionally aligned you and your partner really are.
Washington Post
an hour ago
- Washington Post
Trump says he's unlikely to urge Israel to halt airstrikes
We and our third-party partners process personal data including through the use of cookies, pixels, and other tracking technologies to provide, analyze, and improve our services; personalize your experience (including content); and personalize ads on and off the services. Learn more and manage your preferences at our Privacy Policy
New York Times
an hour ago
- New York Times
Pilot Killed in Plane Crash Had Lifted Wheel to Dodge a Turtle, N.T.S.B. Says
The pilot of a small plane who was killed in a crash this month in North Carolina had lifted a wheel after landing to spare a turtle on the runway, the National Transportation Safety Board said in a preliminary report released on Friday. The pilot and one passenger were killed when the plane crashed just before noon on June 3 near Sugar Valley Airport in Mocksville, N.C., about 60 miles north of Charlotte, the report said. Another passenger was severely injured. The N.T.S.B. said in its report that a communications officer pointed out the turtle to the pilot as the plane returned to the airport and turned to prepare to land on a runway. The pilot landed but then lifted the Universal Stinson 108 plane's right wheel to avoid the turtle. The communications operator reported that she heard the pilot advance the throttle after lifting the wheel. She said that she lost sight of the plane after that. A man cutting the grass at the end of the runway said that he saw the pilot lift the wheel to spare the turtle, the report said. He then saw the plane's wings begin to rock back and forth before it took off again. The man lost sight of the plane after it passed behind a hangar, but said he heard a loud crash and saw smoke, according to the report. The plane crashed in a heavily forested area about 250 feet past the runway and caught fire. It was wedged between several trees and remained intact aside from a few pieces of fabric, the report said. It was unclear whether the pilot's decision to lift the tire to avoid the turtle caused the crash. The N.T.S.B., which said it does not identify the victims in its reports, did not list a probable cause. A final N.T.S.B. report on the crash could take one to two years to complete, the board said. The registered owner of the plane listed on a Federal Aviation Administration website did not immediately respond to a phone message on Friday seeking comment.
