null Skip to main content

GF 108 Tedlar - 1 mil Satin Clear Anti-Graffiti, Clear Permanent Adhesive

$159.95 - $649.95
Financing Options:

GF 108 Tedlar® by DuPont™ is a satin clear 1.0 mil transparent PVF film coated with a solvent permanent pressure sensitive adhesive on a 53# liner. Recommended for use in smooth substrate laminating applications requiring extended resistance to UV exposure, color stability or abrasion resistance. GF 108 made with Tedlar® is graffiti resistant.

  • SUPERIOR PROTECTION for graphics and decals
  • DEFENDS AGAINST permanent markers and spray paint
  • EASY TO CLEAN withstands harsh chemicals
  • ENHANCED DURABILITY and abrasion resistance
  • LONG-LASTING COLOR STABILITY for extended UV exposure
  • UP TO 10 YEARS of outdoor durability

 

APPLICATIONS

  • General Signage
  • POP & Indoor Signage
  • Windows
  • Walls
  • Vehicle Graphics
  • Transit Advertising

INK COMPATIBILITY

  • Not Applicable

 

Does GF 108 protect from UV rays?

GF 108 is designed to extend the exposure resistance of graphics, decals, and nameplates. This overlay will protect inks and graphics from fading caused by exposure to UV radiation.

 

What types of graffiti does GF 108 protect from?

GF 108 Tedlar® film is resistant to permanent markers, spray paint, and harsh chemicals. Cleaners such as MEK and Acetone may be used and have no adverse effects on the film.

 

Will GF 108 Tedlar conform to a textured substrate or complex curves?

GF 108 Tedlar® is designed for smooth surface and substrate applications only. The PVF film is not suitable for use as a laminate on textured print materials (such as WallMark™ HTR textures or GraphiTex® wall fabrics), and it will not conform to complex curves or rivets, even with heat.

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