null Skip to main content

GF 210 - 3.4 Mil Matte White

Item#Item NameRegular PriceSale PriceQty

GF 210 is a 3.4 mil polymeric matte white flexible calendered vinyl film with a removable high-performance pressure sensitive acrylic adhesive on a 90# layflat liner. This film is designed to accept a variety of solvent-based, eco-solvent, latex and UV curable inks common to wide format digital printing systems. The 90# liner offers excellent product layflat in a variety of ambient conditions along with ease of application of large format graphics. The combination of vinyl and adhesive allows removability of the film from most common commercial tile floors for up to 6 months under normal conditions.

APPLICATIONS

  • POP & Indoor Signage
  • Floors

INK COMPATIBILITY

  • Solvent
  • Eco-Solvent
  • Latex
  • UV Curable
  • Screen
  • Offset (UV Curable)

What applications are GF 210 intended for?

GF 210 Traffic Graffic® is designed for temporary floor signs, decals, and point of purchase advertising. A laminate is required to provide protection to the graphics. UL 410 approved overlaminates for slip resistance are GF 109, GF 211, GF 213 and GF 217.

Can I use GF 210 on a floor without lamination?

No. Laminates are needed to ensure non-slip properties of printed graphics.

Can I leave the graphics on the floor past 6 months?

The graphics will stick to the surface and remove clean up to 6 months. Note that after 6 months the graphics will require increasingly more force to remove.

// 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