null Skip to main content

GF 213 Traffic Graffic - 3.75 mil Clear Flexible Embossed Polypropylene

Item#Item NameRegular PriceSale PriceQty
GF 213 Traffic Graffic - 3.75 mil Clear Flexible Embossed Polypropylene

GF 213 is a 3.75 mil clear embossed polypropylene film designed for use as an economical protective laminate for Traffic Graffic® decals. This non-glare laminate is also an environmentally friendly alternative to vinyl films. GF 213 laminate offers a permanent acrylic, pressure sensitive adhesive formulated for exceptional clarity and bond for printed graphic applications. It is intended for use as a laminating film for producing short term indoor Traffic Graffic™ floor decals, table and counter top applications. GF 213 is also approved for indirect food contact. The adhesive is formulated to adhere to most common printing inks. GF 213 has been rated for slip resistance based on multiple testing methods. UL 410 approved for slip resistance on interior floors and commercial carpets.

 

APPLICATIONS

  • POP & Indoor Signage
  • Floors

INK COMPATIBILITY

  • Not Applicable

What types of applications is GF 213 good for?

GF 213 is intended for use in producing Traffic Graffic® floor decals as well as counter mats, mouse pads, and other graphic applications.
 

Does GF 213 bond to all ink types?

The permanent adhesive is formulated to adhere to most common printing inks. Test before production.
 
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