The hubba gourd was a type of melon that grew in rock recesses on the planet of Tatooine. Although its juice was sour and difficult to digest for Humans, the hubba gourd was the main staple foodstuff of the Jawas and the Tusken Raider, the two sentient species native to Tatooine. The name happens to be a translation from the Jawaese phrase: "The Staff of Life".[4]

Biology and appearanceEdit

Unripe hubbas

Obi-Wan Kenobi manipulating unripe hubba gourds

Hubba gourds were tough-skinned melons,[5] that grew in the shadows of the cliffs on Tatooine. They could be round[3] or elongated.[1] Those fruits were normally covered with tiny reflective crystals that protected them from excessive solar exposure.[5] The gourd's interior was filled with tough, stringy fibers that contained a sour fluid.[3] During their growing season, hubba gourds were colored green,[6] and they would eventually take a yellowish hue.[3] When ripe, those fruits also exhaled a distinctive smell.[7] The seeds of the hubba gourd were pale and transparent.[8]


The hubba gourd was prime food for Tusken Raiders and Jawas; the latter species found it particularly delicious when roasted.[9] In fact, the word hubba itself was Jawaese for "the staff of life," indicating how important it was to that species' survival. Despite often finding the gourd hard to digest and bitter, other species could also consume it, including Humans,[1] Geranitess and Askajians.[3] Additionally, a drink,[10] a type of bread[11] and a snack could be made from hubba gourds.[12]

Wimateeka, a Jawa leader of the Nkik clan, once contracted a number of hunters to eliminate wild animals that were attacking his clan's supply of hubba gourds.[13]

Momaw Nadon was known to have been working on a hybrid hubba gourd.[8]



Notes and referencesEdit

In other languages

Ad blocker interference detected!

Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.