null Skip to main content

GF 216 - 3.2 mil Gloss White, Clear Permanent Adhesive

Item#Item NameRegular PriceSale PriceQty
GF 216 - 3.2 mil Gloss White, Clear Permanent Adhesive

GF 216 is a 3.0 mil gloss white calendared vinyl with a clear acrylic pressure sensitive adhesive on a 90# layflat liner. This vinyl is designed to accept a variety of solvent, eco solvent, latex and UV curable inks common to wide format digital printing systems. The adhesive produces permanent bonds to a variety of common substrates used in graphics applications.

 

APPLICATIONS
  • General Signage
  • POP & Indoor Signage
INK COMPATIBILITY
  • Solvent
  • Eco-Solvent
  • Latex
  • UV Curable
  • Screen
  • Offset (UV Curable)
 

What applications are GF 216 intended for?

GF 216 is designed for interior or exterior signage, decals, nameplates, point-of-purchase displays and general signage.
 

Can GF 216 be removed?

Most decals can be removed with some effort, even if they have a permanent adhesive. GF 216 has a standard permanent adhesive that works on a variety of surfaces. This adhesive is permanent and will not remove cleanly, but any adhesive transfer or residue can be cleaned up easily with standard adhesive removers.
Free Local Delivery
Next Day Delivery
Order By 5PM CST
Save 2% On Pickup
Low Rate Financing
Flat Rate Shipping
Join Our Mailing List

Sign up to receive updates, special offers, and discounts!

// Uses React's native (unpatched) value setter + a real dispatched event, // so the app's own onChange / validation / append logic fires correctly. // build the visible field the user will actually type into // copy the real field's classes + computed styles so it looks identical // preload with existing value (formatted) if the real field already has one // hide the real field visually but keep it in the DOM and functional, // so your app's own validation / append event still works as before // place the visible field right where the real one used to be // send only the plain digits to the real field — this matches what // the numeric field type expects, so no "invalid phone number" error // keep focus/blur events flowing to the real field too, in case your // app's validation triggers specifically on those