top of page
Writer's pictureLinda Moore Kurth

Chile Con Queso from New Mexico

Chile Con Queso

One of the first New Mexico recipes I learned to make when I moved to New Mexico was this Chile Con Queso which was served at about every party and get-together I attended. This concoction was never meant to be a health food. The main ingredient is Velveeta. 

Now you may ask, as I did, what Velveeta is doing in a traditional New Mexican dish. My research tells me it was the first cheese that didn’t need to be refrigerated, and a boon to those households that had little refrigeration. 

We made this for our family “Thanksmas” last week, and had some leftover, so I put it in the ham and been soup I made. Delicioso!  T’would be good in posole too.

 

Servings: 8    Serving size: 1/4 cup    Preparation time: 30 minutes    Total time: 45 minutes




Ingredients 1 cup onions, minced 2 medium garlic cloves, minced 3 tablespoons of butter 15 ounces tomato sauce 4 ounces canned diced green chiles. 3 teaspoons N.M. chile powder   ​(or 2 tablespoons Secret Santa Fe Red Chile Sauce) 8 ounces Velveeta cheese

Directions 1. In a medium sucepan, saute onion and garlic in butter until soft. 2. Add the tomato sauce and chile powder and simmer for thirty ninutes. 3. Add the Velveeta and the green chiles. Stir over medium to low heat until the cheese is melted. 4. Serve in a small crockpot or cheese fondue pot to keep warm, along with a basket of corn tortillas. 

Good cooking to you!  ​Linda ​​​​​Note: Would you like a printout of this and other recipes? These directions may help: Use your mouse to select only the text you want to copy rather than the entire page. Then press Ctrl+C, open your Word program and press Ctrl+V to paste the semi-formatted text. Print it from there.

5 views0 comments

Recent Posts

See All

Layered Bean and Beet Salad

This layered salad shows off well in a clear glass bowl. It’s a dish that consistently showed up at our family potlucks. It’s still just...

Comments

Couldn’t Load Comments
It looks like there was a technical problem. Try reconnecting or refreshing the page.
bottom of page